Log inTalk to us

Read a rollback and the charger's reconnect status

get/v1/tenants/{tenant_id}/migration/rollbacks/{rollback_id}
Requires an API key

status: pending, applied_socket_open, applied, failed, superseded or expired. reconnect: whether the charger reconnected to the previous platform through the proxy. Requires stations:read. Errors: 404 migration_rollback_not_found. See Errors and statuses.

Path parameters

  • tenant_idintegerRequired
  • rollback_idstringRequired
    Pattern ^mrb_[0-9a-f]{32}$

Returns · 200

  • idstringRequired
    Ivora's identifier of this rollback (mrb_...).
  • tenant_idintegerRequired
  • station_idintegerRequired
  • namestringRequired
    The station's OCPP connection name.
  • statusenumRequired
    pending: recorded, waiting for the charger proxy to switch the route. applied_socket_open: the proxy routes the charger to the previous platform, but a connection to Ivora is still open; the proxy closes it and the rollback becomes applied (only then is the event emitted). applied: the proxy routes the charger to the previous platform and no connection to Ivora is open. failed: the proxy could not switch it (detail); ask again, or Ivora on-call rolls it back by hand. superseded: Ivora staff moved the charger to Ivora again after it was asked, so it was not applied. expired: the proxy did not apply it within 24 hours (it was unreachable); Ivora on-call rolls it back by hand.
    One of pending, applied_socket_open, applied, failed, superseded, expired
  • reconnectenum | nullRequired
    Whether the charger reconnected to the previous platform through the proxy, from the proxy's latest report: waiting_for_switch (pending), reconnecting (within two minutes of the switch), reconnected (a connection to the previous platform is up), not_connected (no connection two minutes after the switch), still_on_ivora (a connection to Ivora is still open, also while applied_socket_open), superseded (the charger was moved to Ivora again since), unknown (no proxy report since the switch). Null when failed, superseded or expired.
    One of waiting_for_switch, reconnecting, reconnected, not_connected, still_on_ivora, superseded, unknown
  • reasonstringRequired
  • requested_bystringRequired
    Who asked for it: user:<id>, key:<id> or app:<id>.
  • team_idstring | nullRequired
    The project's team.
  • sourceenumRequired
    tenant: the project's own administrators; ivora: Ivora staff.
    One of tenant, ivora
  • requested_atstringRequired
  • rolled_back_atstring | nullRequired
    When the proxy switched the route (its own clock), once applied.
  • settled_atstring | nullRequired
    When Ivora recorded the current status (the proxy's result, the socket closing, the supersession or the expiry).
  • detailstring | nullRequired
    The proxy's note on the result, such as why it failed.
  • event_idstring | nullRequired
    The migration.charger_rolled_back event, once applied.
  • migration_idstring | null
    The migration workspace of the station (/v1/migrations/{migration_id}), when it is in one.
GET /v1/tenants/{tenant_id}/migration/rollbacks/{rollback_id}
curl --fail-with-body "https://api.ivoracharge.com/v1/tenants/1042/migration/rollbacks/mrb_0123456789abcdef0123456789abcdef" \
  -H "Authorization: Bearer $IVORA_API_KEY"
Response · 200JSON
{
  "id": "id_0123456789abcdef",
  "tenant_id": 1042,
  "station_id": 1,
  "name": "bay-01",
  "status": "pending",
  "reconnect": "waiting_for_switch",
  "reason": "string",
  "requested_by": "string",
  "team_id": "team_0123456789abcdef",
  "source": "tenant",
  "requested_at": "2026-09-30T17:00:00Z",
  "rolled_back_at": "2026-09-30T17:00:00Z",
  "settled_at": "2026-09-30T17:00:00Z",
  "detail": "string",
  "event_id": "event_0123456789abcdef",
  "migration_id": "migration_0123456789abcdef"
}
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.