REST API

CleverEV’s public REST API lets a server-to-server integration read and manage charger, location, charging-session, and webhook resources. Calls are authenticated with an API key and scoped with the organization-id header. The operation reference is the contract for individual paths and fields; these guides cover workflows that span more than one operation.

How scope and resource IDs fit together

The API key authenticates the caller. The required organization-id header selects which tenant’s data and permissions apply to a request. When an operation returns a resource ID, pass that value to a later operation that accepts it; the operation reference shows which paths do.

List operations let you narrow a collection with filters, sort it, and retrieve it page by page. Some list operations can also attach time-bucketed metrics to each resource. That aggregation is per resource, not a single organization-wide total.

Choose a guide

• Make a first API request — authenticate, list chargers, then use a returned charger ID in a detail request.
• Request format — base URL, headers, timestamps, and body formats.
• Select an organization — scope requests to an organization your key is authorized to access.
• Filter, sort, and paginate results — build list queries and traverse results predictably.
• Aggregating list results over time — add time-bucket metrics to list records.