Skip to content

Verify Tracking Domain

Re-check DNS and certificate status for a tracking domain.

POSThttps://api.foxreach.io/api/v1/tracking-domains/{domain_id}/verify

Requires an API key with the write scope.

There is no request body. The domain becomes active when the hostname and its certificate are both active. Call it again after DNS has had time to propagate.

Path Parameters#

domain_idstringpathrequired

The tracking domain identifier.

Response#

dataobject

The tracking domain with its refreshed status.

Show data
idstring
Tracking domain identifier.
domainstring
The tracking subdomain.
statusstring
pending, verifying, active or failed.
cnameTargetstring
The hostname to point your CNAME record at.
sslStatusstring
Certificate status, for example pending_validation or active. null until provisioning has run.
failureReasonstring
Why provisioning or verification failed, or null.
verifiedAtstring
ISO 8601 timestamp, or null.
lastCheckedAtstring
ISO 8601 timestamp, or null.
createdAtstring
ISO 8601 timestamp.

Errors#

StatusDescription
401Missing, invalid, revoked or expired API key
403API key does not have the required scope: write
404Tracking domain not found, or it belongs to another workspace
501Custom tracking domains are not enabled on this environment.

Rate Limit#

  • 100 requests per minute, per API key. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (unix epoch seconds).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).

For client-side patterns (Retry-After, exponential backoff, monitoring X-RateLimit-Remaining), see Rate Limiting.

Was this page helpful?
View as MarkdownLast updated November 2, 2026