platform-transfers

GET /v1/platform-transfers/{transferId}

One transfer and its progress.

All platform-transfers endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks billing.view; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/platform-transfers/{transferId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Parameters

NameTypeRequiredWhat it is
transferId (path)stringYes—

Response

NameTypeRequiredWhat it is
idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
source_platformstringYes—
source_platform_namestringNo—
target_platformstringYes—
target_platform_namestringNo—
source_urlstringYes—
target_site_idobjectNo—
tier_codestringYes—
tier_namestringNo—
entity_count_estimateintegerNo—
statusPlatformTransferStatusYes—
status_labelstringNo—
price_amount_minorintegerYes—
price_currencystringYes—
redirects_mappedbooleanNo—
redirect_countintegerNo—
canonicals_verifiedbooleanNo—
sitemap_submittedbooleanNo—
structured_data_preservedbooleanNo—
seo_checks_completebooleanNo—
customer_notestringNo—
sla_due_atobjectNo—
created_atstringYes—
completed_atobjectNo—
eventsPlatformTransferEvent[]NoThe customer-visible trail only. Staff notes name vendors and what a job cost us, and never appear here.

Errors this endpoint can return

401 · 403 · 404 · 429