Skip to main content
GET
Get the record-import outcome

Authorizations

Authorization
string
header
required

Request signing with an access key issued to a service account. An HMAC-SHA256 over a canonical form of the request, close to AWS SigV4. The basaltic CLI signs for you.

Send Authorization, X-Date (UTC, YYYYMMDDTHHMMSSZ) and X-Nonce (random per request); add X-Content-Sha256 to bind a body, and X-Amz-Security-Token when using temporary credentials.

<region> is the region code you are calling, or global for the global services. A signature is valid for 5 minutes from X-Date, and mutating requests are replay-guarded on the nonce.

Full signing procedure, including a working implementation: https://docs.basaltic.sh/authentication

Rate limits

There is no global request budget. A limit applies only where an operation documents a 429, and that operation says what it counts. Those responses carry X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and, on a 429, Retry-After — read them rather than hard-coding a number. Retrying before Retry-After is refused and extends the window. Everything else is bounded by quota, not by request rate.

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.