Log inTalk to us
Developer tools

Read a migration request

get/v1/migration-requests/{request_id}
Requires an API key

Ivora platform administrators, and the requester; Ivora platform support gets 403 (on another's request), anyone else 404. Errors: 404 migration_request_not_found. See Errors and statuses.

Path parameters

  • request_idstringRequired
    Pattern ^mrq_[0-9a-f]{32}$

Returns · 200

  • idstringRequired
    mrq_...
  • tenant_idintegerRequired
    The project the migration is for.
  • team_idstring | nullRequired
    The project's team when the request was made.
  • statusenumRequired
    open: waiting for Ivora. workspace_created: Ivora opened the migration (migration_id). declined: Ivora declined it (decision_reason).
    One of open, workspace_created, declined
  • source_platformstringRequired
  • chargers_estimateinteger | nullRequired
  • sites_estimateinteger | nullRequired
  • target_fromstring | nullRequired
  • target_tostring | nullRequired
  • partnerobject | nullRequired
    Shown to Ivora staff and the requester only; null for anyone else.
    Child attributes
    • namestringRequired
      The migration partner or installer.
      1–120 characters
    • emailstring | null
      Their contact address.
      3–254 characters · Pattern ^[^@\s]+@[^@\s]+\.[^@\s]+$
  • notesstring | nullRequired
    Shown to Ivora staff and the requester only; null for anyone else.
  • requested_bystringRequired
    The requester (user:...).
  • created_atstringRequired
  • updated_atstringRequired
  • migration_idstring | nullRequired
    The migration Ivora opened for it.
  • decision_reasonstring | nullRequired
    Why Ivora declined it.
  • decided_atstring | nullRequired
GET /v1/migration-requests/{request_id}
curl --fail-with-body "https://api.ivoracharge.com/v1/migration-requests/mrq_0123456789abcdef0123456789abcdef" \
  -H "Authorization: Bearer $IVORA_API_KEY"
Response · 200JSON
{
  "id": "id_0123456789abcdef",
  "tenant_id": 1042,
  "team_id": "team_0123456789abcdef",
  "status": "open",
  "source_platform": "string",
  "chargers_estimate": 1,
  "sites_estimate": 1,
  "target_from": "string",
  "target_to": "string",
  "partner": {
    "name": "bay-01",
    "email": "developer@example.com"
  },
  "notes": "string",
  "requested_by": "string",
  "created_at": "2026-09-30T17:00:00Z",
  "updated_at": "2026-09-30T17:00:00Z",
  "migration_id": "migration_0123456789abcdef",
  "decision_reason": "string",
  "decided_at": "2026-09-30T17:00:00Z"
}
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.