CustomDomain™ docs
API referenceConnections

The CustomDomain™ services the domain uses

GET
/connections/{id}/services

Every CustomDomain™ service with whether this domain uses it, computed from stored facts: DNS connect (with the rail that wrote the records and the access CustomDomain™ holds), managed DNS, edge serving, the HTTPS certificate, Power, monitoring, automatic repair, redirects, email records and CAA. state is active, pending (set up, not serving yet), attention (in use, and something needs a person), paused (automatic repair where CustomDomain™ holds the access but the deployment has not switched repair on, MONITOR_AUTO_REPAIR) or inactive. An end user's widget token (scope connect) reads this only when it is bound to the domain and minted with the connection's own end_user_ref; use an API key otherwise.

Authorization

AuthorizationBearer <token>

Short-lived widget JWT minted server-side via POST /v1/tokens. Scoped to one application (and optionally one domain).

In: header

Path Parameters

id*string

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/connections/string/services"
{  "connection_id": "string",  "application_id": "string",  "domain": "string",  "status": "string",  "provider": "string",  "provider_name": "string",  "access": {    "mode": "kept",    "via": "managed_dns",    "detail": "string",    "connected_via": "string"  },  "services": [    {      "id": "dns_connect",      "name": "string",      "active": true,      "state": "active",      "detail": "string",      "since": "2019-08-24T14:15:22Z"    }  ],  "active_count": 0}
{  "code": "string",  "title": "string",  "details": "string"}
{  "code": "string",  "title": "string",  "details": "string"}
{  "code": "string",  "title": "string",  "details": "string"}