Verify Tracking Domain
Re-check DNS and certificate status for a tracking domain.
POST
https://api.foxreach.io/api/v1/tracking-domains/{domain_id}/verifyRequires 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_idstringpathrequiredThe tracking domain identifier.
Response#
dataobjectThe tracking domain with its refreshed status.
Show data
idstringTracking domain identifier.
domainstringThe tracking subdomain.
statusstringpending, verifying, active or failed.cnameTargetstringThe hostname to point your CNAME record at.
sslStatusstringCertificate status, for example
pending_validation or active. null until provisioning has run.failureReasonstringWhy provisioning or verification failed, or
null.verifiedAtstringISO 8601 timestamp, or
null.lastCheckedAtstringISO 8601 timestamp, or
null.createdAtstringISO 8601 timestamp.
Errors#
| Status | Description |
|---|---|
401 | Missing, invalid, revoked or expired API key |
403 | API key does not have the required scope: write |
404 | Tracking domain not found, or it belongs to another workspace |
501 | Custom 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, andX-RateLimit-Reset(unix epoch seconds). - A
429response includes aRetry-Afterheader (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