Search the tenant's RFID tokens
post/v1/tenants/{tenant_id}/tokens/search
Requires an API key
Requires tokens:read. Read-only, so it takes no Idempotency-Key. The filters of GET /v1/tenants/{tenant_id}/tokens (id_token, external_reference, status, type, after, limit) in a JSON body, with the same results: a card's value stays out of the URL, and so out of proxy and access logs. id_token matches case-insensitively, as chargers are authorized.
Path parameters
- tenant_idintegerRequired
Request body
- id_tokenstring | nullReturn only the token with this value, matched case-insensitively as chargers are authorized.Pattern
^[\x21-\x7e]{1,36}$ - external_referencestring | nullReturn only the token carrying this external_referencePattern
^[A-Za-z0-9][A-Za-z0-9_.:/-]{0,127}$ - statusenum | nullOne of
Accepted,Blocked,Expired - typeenum | nullOne of
Central,eMAID,ISO14443,ISO15693,KeyCode,Local,MacAddress,NoAuthorization - afterintegerThe next_cursor of the previous pageDefault
0· Minimum 0 - limitintegerDefault
50· Minimum 1 · Maximum 100
Returns · 200
- dataarray of TokenRecordRequired
Child attributes
- idintegerRequired
- tenant_idintegerRequired
- id_tokenstringRequired
- typestring | nullRequired
- statusstringRequiredAccepted, Blocked or Expired through this API; tokens written by other tools may carry another OCPP status.
- expires_atstring | nullRequired
- labelstring | null
- external_referencestring | null
- metadataobjectYour own key/value pairs (strings), such as a site host or a contract ID: at most 50 keys of 1-40 characters of A-Z, a-z, 0-9, underscore, period and hyphen, values of at most 500 characters. Never secrets or personal data. Never published to OCPI roaming partners.
- ocpp16_compatiblebooleanRequiredFalse when id_token is longer than the 20 characters an OCPP 1.6 idTag allows.
- created_atstring | nullRequired
- updated_atstring | nullRequired
- next_cursorintegerRequired
POST /v1/tenants/{tenant_id}/tokens/search
curl --fail-with-body -X POST "https://api.ivoracharge.com/v1/tenants/1042/tokens/search" \
-H "Authorization: Bearer $IVORA_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'Response · 200JSON
{
"data": [
{
"id": 1,
"tenant_id": 1042,
"id_token": "string",
"type": "string",
"status": "string",
"expires_at": "2026-09-30T17:00:00Z",
"label": "string",
"external_reference": "property:1001",
"metadata": {},
"ocpp16_compatible": false,
"created_at": "2026-09-30T17:00:00Z",
"updated_at": "2026-09-30T17:00:00Z"
}
],
"next_cursor": 1
}Requires an approved production API keyProduction access starts with a request, a short meeting with Ivora and a card on file, after which Ivora staff grant your account access. How to request access
Try itproduction · api.ivoracharge.com
Paste a production api key (iv_live_…). Create keys in Developer tools. The key stays in this page's memory, is sent only to https://api.ivoracharge.com and clears when you reload. Test keys are refused.
POST is a write: you confirm the method, path and project before it is sent, with a generated Idempotency-Key.



