Log inTalk to us
Developer tools

List a station's recorded OCPP 1.6 shadow transaction IDs

get/v1/tenants/{tenant_id}/stations/{station_id}/shadow/transactions
Requires an API key

The pairs the charger proxy recorded for one of the project's stations, oldest first; control_transaction_id or copy_transaction_id finds one (the proxy looks up a control ID it lost). Paginate with after=next_cursor. Requires stations:read, or the project's charger proxy key (migration:proxy). Another project's station reads as unknown. Read-only. Errors: 404 station_not_found. See Errors and statuses.

Path parameters

  • tenant_idintegerRequired
  • station_idintegerRequired
    Greater than 0

Query parameters

  • control_transaction_idstring | null
    Pattern ^-?[0-9]{1,10}$
  • copy_transaction_idstring | null
    Pattern ^-?[0-9]{1,10}$
  • afterinteger
    Default 0 · Minimum 0
  • limitinteger
    Default 100 · Minimum 1 · Maximum 500

Returns · 200

  • dataarray of ShadowTransactionRequired
    Child attributes
    • station_idintegerRequired
    • tenant_idintegerRequired
    • control_transaction_idstringRequired
      The transactionId the controlling platform assigned; the charger uses it in MeterValues and StopTransaction.
    • copy_transaction_idstringRequired
      The transactionId Ivora's core assigned on the copy link: the proxy rewrites the charger's control ID to it on that link.
    • connector_idintegerRequired
    • started_atstringRequired
    • meter_start_whinteger | nullRequired
    • control_statusstring | nullRequired
    • copy_statusstring | nullRequired
    • stopped_atstring | nullRequired
    • meter_stop_whinteger | nullRequired
    • stop_reasonstring | nullRequired
    • energy_whinteger | nullRequired
      meter_stop_wh - meter_start_wh: the charger's registers, Wh; null until both are known.
    • recorded_bystringRequired
    • created_atstringRequired
    • updated_atstringRequired
  • next_cursorintegerRequired
GET /v1/tenants/{tenant_id}/stations/{station_id}/shadow/transactions
curl --fail-with-body "https://api.ivoracharge.com/v1/tenants/1042/stations/1/shadow/transactions" \
  -H "Authorization: Bearer $IVORA_API_KEY"
Response · 200JSON
{
  "data": [
    {
      "station_id": 1,
      "tenant_id": 1042,
      "control_transaction_id": "control_transaction_0123456789abcdef",
      "copy_transaction_id": "copy_transaction_0123456789abcdef",
      "connector_id": 1,
      "started_at": "2026-09-30T17:00:00Z",
      "meter_start_wh": 7500,
      "control_status": "string",
      "copy_status": "string",
      "stopped_at": "2026-09-30T17:00:00Z",
      "meter_stop_wh": 7500,
      "stop_reason": "string",
      "energy_wh": 7500,
      "recorded_by": "string",
      "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.