Skip to main content
POST
Migrate email subscribers

Restrictions

Usage

  • Requires the On-call Professional plan; other accounts get AccessDenied.
  • Runs asynchronously and returns job_id; poll GET /status-page/migration/status. Only one migration job per account can run at a time.
  • Run it after POST /status-page/migrate-structure for the same source page: component subscriptions are mapped to the components that migration created, and a subscriber whose components cannot be mapped is subscribed to all components.
  • Non-email, quarantined, and address-less subscribers are skipped and counted in progress.subscribers_skipped; recipients already subscribed on the target page are left unchanged.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for starting an Atlassian Statuspage email subscriber migration job.

api_key
string
required

Atlassian Statuspage API key with access to the source page.

source_page_id
string
required

Atlassian Statuspage source page ID; only letters, digits, _, and - are accepted.

target_page_id
integer<int64>
required

Flashduty target status page ID that will receive the imported 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

Result of starting a migration job.