Log inTalk to us
Developer tools

List a migration's team keys

get/v1/migrations/{migration_id}/keys
Requires an API key

Newest first, never the secrets. The client and Ivora support see every team's keys; a team's owners and admins see their own team's. Signed-in users only: an API key cannot manage keys. The key acts on this migration's routes and GET /v1/access only; every project route (/v1/tenants/...) refuses it. On every request it holds the scopes its creator's current role in the migration still allows, so a downgrade takes effect at once and the key stops when they leave the team or the team leaves the migration (which also revokes its keys). Errors: 403 migration_key_not_permitted, 404 migration_not_found. See Errors and statuses.

Path parameters

  • migration_idstringRequired
    Pattern ^mig_[0-9a-f]{32}$

Returns · 200

  • dataarray of MigrationKeyRequired
    Child attributes
    • idstringRequired
      key_...
    • labelstringRequired
    • prefixstringRequired
      The key's first 16 characters, to recognise it; the secret is shown only when it is created.
    • scopesarray of enumRequired
    • migration_idstringRequired
    • team_idstringRequired
      The participant team the key belongs to.
    • created_bystringRequired
    • created_atstringRequired
    • api_versionstringRequired
    • revokedbooleanRequired
    • revoked_atstring | nullRequired
    • revoked_bystring | nullRequired
GET /v1/migrations/{migration_id}/keys
curl --fail-with-body "https://api.ivoracharge.com/v1/migrations/mig_0123456789abcdef0123456789abcdef/keys" \
  -H "Authorization: Bearer $IVORA_API_KEY"
Response · 200JSON
{
  "data": [
    {
      "id": "id_0123456789abcdef",
      "label": "string",
      "prefix": "string",
      "scopes": [
        "migration:read"
      ],
      "migration_id": "migration_0123456789abcdef",
      "team_id": "team_0123456789abcdef",
      "created_by": "string",
      "created_at": "2026-09-30T17:00:00Z",
      "api_version": "string",
      "revoked": false,
      "revoked_at": "2026-09-30T17:00:00Z",
      "revoked_by": "string"
    }
  ]
}
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.