Skip to content
DocsGo to Dashboard
Authenticating public API requests

GET /v1/public-api/domains (requires the "read" scope) lists your tenant's connected domains

The smallest useful call: authenticate with a service-account token and read back the domains your workspace has connected, with their current status.

The request#

curl -s https://api.example.com/v1/public-api/domains \
  -H "Authorization: Bearer sat_your-token"

The route resolves the bearer token, checks it is active, unexpired, and holds the read scope, then returns the tenant's domains. A missing credential answers Missing bearer service-account token.; anything invalid, expired, revoked, or missing the scope answers Invalid, expired, revoked, or out-of-scope service-account token.

The response#

{
  "domains": [
    {
      "id": "...",
      "hostname": "www.acme.com",
      "status": "LIVE",
      "accelerationEnabled": true,
      "configurationVersion": 12,
      "createdAt": "..."
    }
  ]
}

Only the fields an integration needs are selected — id, hostname, status, acceleration flag, current configuration version, and created-at. Note this route requires a service-account token, not the tenant API key: the two are different credentials with different homes (see Authenticate the request for where the tenant key is used).

Back to Authenticating public API requests