Selecting an organization

Use this when configuring an integration or when a service acts for more than one CleverEV organization.

Choose the organization ID

The organization-id header is the tenant scope for the request: it determines which organization’s records are queried and which permissions are evaluated. Supply the organization’s identifier, not its display name, a charger ID, or a session ID. If you do not know the identifier, get it from the organization administrator or the integration setup that issued the API key.

A valid API key does not by itself grant access to every organization. The key must be authorized for the organization ID you send. For a multi-organization integration, keep the mapping between your customer account and its authorized organization ID on the server; do not trust a caller-supplied ID without checking that mapping.

Send the scope on every request

API_BASE='https://api.cleverev.net'
API_KEY='<API_KEY>'
ORGANIZATION_ID='<ORGANIZATION_ID>'
COMPATIBILITY_DATE='2026-01-01'

curl --get "$API_BASE/chargers" \
  --header "Authorization: Bearer $API_KEY" \
  --header "organization-id: $ORGANIZATION_ID" \
  --header "compatibility-date: $COMPATIBILITY_DATE" \
  --header 'Accept: application/json'

Use the same organization scope for follow-up requests that use IDs returned from the list. If the request is rejected, check the HTTP status and error body, then verify both the key’s authorization and the selected organization. See Request format for the full header contract.