/projects/{project_id}/branches/{branch_id}/custom-domainsList the custom domains on a branchLists all custom domains registered on the branch, across every target entity.
Note: This endpoint is currently in Beta.
Parameters
project_idstringpathrequiredThe Neon project ID
branch_idstringpathrequiredThe Neon branch ID
cursorstringqueryA cursor to use in pagination. A cursor defines your place in the data list. Include `response.pagination.next` in subsequent API calls to fetch next page of the list.
limitintegerquerySpecify a value from 1 to 1000 to limit number of domains in the response
Responses
allOf · 2 options
custom_domainsarray of objectrequiredShow child attributes
Show array items
binding_statusstringWhether Neon's internal routing for the domain is published: `pending`, `present`, or `missing`. `missing` is an internal fault surfaced for support. Not an `enum`.
cname_targetstringrequiredThe hostname the customer must point their custom domain at with a CNAME record. Empty when the serving region has no custom-domains front door configured. This is the activation input: point DNS here and the domain goes live (see `status`) once a certificate is issued on the first request.
dns_statusstringThe DNS + CAA portion of the check: `pending` (no records yet), `ok` (resolves to our edge and the CA is authorized), `misconfigured` (your CNAME does not resolve to our edge), or `caa_blocked` (your CAA records forbid Let's Encrypt). Not an `enum`.
domainstringrequiredThe registered custom domain (normalized, lowercase).
entity_idstringrequiredThe target entity's identifier within the branch. For `function` this is the function slug.
entity_typestringrequiredThe kind of branch entity the domain targets. Possible values: `function` (v1 supports only `function`). Not an `enum`: new values may ship in later spec versions — treat any undocumented value as unknown.
statusstringThe domain's current validity, computed by a background check: `pending` (still converging — point your CNAME at `cname_target` and wait), `active` (live: DNS resolves to the edge, the CA is authorized, and routing is published), or `error` (a fixable problem — see `status_reason`). Not an `enum`: treat any undocumented value as unknown. May be absent briefly right after registration.
status_reasonstringA short, stable machine-readable reason for a non-active `status` (e.g. `cname-not-pointing-at-edge`, `caa-blocks-lets-encrypt`, `binding-missing`), suitable for keying an actionable hint. Empty when active or pending.
paginationobjectTo paginate the response, issue an initial request with `limit` value. Then, add the value returned in the response `.pagination.next` attribute into the request under the `cursor` query parameter to the subsequent request to retrieve next page in pagination. The contents on cursor `next` are opaque, clients are not expected to make any assumptions on the format of the data inside the cursor.
Show child attributes
nextstringCursor for the next page of results. Pass it as the `cursor` query parameter on the next request. Absent on the last page.
sort_bystringField by which the results were sorted, echoing the request's sort_by parameter.
sort_orderstringSort order active for this page. Pass back as `sort_order` in the next request to maintain consistent ordering. Valid values are `asc` and `desc`.
{
"custom_domains": [
{
"binding_status": "string",
"cname_target": "string",
"dns_status": "string",
"domain": "string",
"entity_id": "string",
"entity_type": "string",
"status": "string",
"status_reason": "string"
}
],
"pagination": {
"next": "string",
"sort_by": "string",
"sort_order": "string"
}
}codestringrequiredmessagestringrequiredError message
request_idstringUnique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.
{
"code": "",
"message": "string",
"request_id": "string"
}