Skip to main content
GET
Get the record-import outcome
Requires the IAM action dns:GetZone. See DNS permissions for the full list, what each one covers, and an example policy.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Path Parameters

zone_id
string<uuid>
required

DNS Zone ID

Response

The import outcome

record_import
object

What came of import_existing_records — reading the domain's records off the provider it is moving away from.

Its own resource, at GET /v1/zones/{zone_id}/record-import, because it describes one event that happened once when the zone was created and never changes afterwards. 404 when the zone was created without asking for an import, which is the ordinary case and not an error.

A failed import is never a failed zone. The zone exists, resolves once delegated, and can be filled in by hand or from a zone file; only the convenience did not happen.