Check a zone's DS at its parent
Whether the zone's DS record is published at its parent, which is what makes DNSSEC take effect. It reads the public DNS, so it can lag a change at your registrar. parentDs is published, missing, mismatch (a DS is there, but not this zone's), stale (DNSSEC is off here and a DS is still published), not_delegated (the domain doesn't use this zone's nameservers yet, so a DS there isn't this zone's), parent_unsigned (the zones above aren't signed, so nothing can validate this one), or unknown (the check didn't finish, or there's nothing to compare).
https://dns-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/zones/{zoneId}/dnssecAuthorization
Path parameters
Returns
200
The check.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.