Skip to main content
GET
/
status-page
/
migration
/
status
Get migration status
curl --request GET \
  --url 'https://api.flashcat.cloud/status-page/migration/status?app_key='
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "job_id": "01KP0311872NVYFRRQ82FW0001",
    "account_id": 2451002751131,
    "source_page_id": "abcdefghij",
    "target_page_id": 5750613685214,
    "phase": "history",
    "status": "completed",
    "progress": {
      "total_steps": 5,
      "completed_steps": 5,
      "components_imported": 8,
      "sections_imported": 3,
      "incidents_imported": 12,
      "maintenances_imported": 2,
      "subscribers_imported": 0,
      "templates_imported": 0,
      "subscribers_skipped": 0
    },
    "created_at": 1766736878,
    "updated_at": 1766740000
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsNone — any valid app_key can call this operation

Authorizations

​
app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Query Parameters

​
job_id
string
required

Migration job ID returned by migrate-structure or migrate-email-subscribers.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

​
request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

​
data
object
required

A migration job's current state and progress.