Skip to main content
POST
Verify a domain
Check the routing and TXT ownership records for one domain. Requires Custom domains: Write (custom_domains.update). Send an empty JSON object or no body; no fields are accepted.

Successful verification

When both records match, Biqli marks DNS verified and queues SSL provisioning:
The actual domain object is complete; it is abbreviated above. DNS verification does not mean HTTPS is ready. Retrieve the domain until status and ssl_status are both active before publishing links that depend on it.

DNS not ready

If either record is missing or has not propagated, the endpoint returns 422 dns_verification_failed:
The two booleans identify which requirement is missing without exposing other DNS records found during lookup. DNS propagation can take time; correct the records, wait, and retry. Verification is idempotent, and repeated successful checks do not queue duplicate active SSL operations.

Shared API behavior

Authentication is workspace-scoped; see Authentication. Errors use the standard envelope and request IDs described in Errors, and requests are subject to Rate limits.

Authorizations

Authorization
string
header
required

A workspace API key beginning with biqli_.

Path Parameters

domain
string
required

Public custom-domain ID. Numeric IDs and hosts are not accepted.

Pattern: ^biq_dom_[0-9A-HJKMNP-TV-Z]{26}$

Body

application/json

The body is of type object.

Response

DNS was verified and SSL is active or provisioning.

verified
boolean
required
records
object
required
domain
object
required
status
string
required
Allowed value: "success"