Skip to main content
Developer Marketing Signatures1.0.0-beta.1

List a signature’s custom domains

Lists hostnames connected to the signature and their customer-facing DNS instructions. Quota usage includes reservations across the token Space.

GET/api/v1/marketing/signatures/{signatureId}/custom-domains

Workspace automation for approved Dashio products. Each token is scoped to one Space and independently granted operations. Requests spend shared minute credits, and selected operation groups also share hourly quotas.

Required token scope is marketing:signature-domains:read. Scopes are independent.

This operation uses 1 credit from a shared budget of 60 credits per token and 300 per Space each UTC minute.

Run these examples on a trusted server with DASHIO_API_TOKEN configured. Use a private terminal when inspecting response data. Examples send one request with a bounded timeout and do not retry automatically.

Authentication

Dashio developer token (HTTP Bearer) API authentication guide

Path parameters

signatureIdstring (uuid)Required

Stable signature UUID.

Query parameters

None documented.

Header parameters

None documented.

Request body

No content type declared

No request body schema is documented.

Responses

Headers on every response

X-Request-Idstring (uuid)Optional

Server-generated ID to include in a support request.

200

Custom domains and current Space allowance.

Response headers

RateLimit-LimitintegerOptional

Per-token capacity in the reported gateway window, expressed in requests of this operation. A shared Space budget also applies. Present when the request reaches the authenticated gateway. Minimum: 1.

RateLimit-RemainingintegerOptional

Requests of this operation remaining under the current token, Space and applicable operation-group quotas. Present when the request reaches the authenticated gateway. Minimum: 0.

RateLimit-ResetintegerOptional

Unix timestamp in seconds when the reported gateway quota resets. Present when the request reaches the authenticated gateway. Minimum: 0.

application/json

configuredbooleanRequired

No field description supplied.

limitintegerRequired

Minimum: 0.

usedintegerRequired

Minimum: 0.

domainsarray of objectRequired

No field description supplied.

400

The request fields, selectors or resource identifiers are invalid.

application/json

statusCodeintegerRequired

Minimum: 400. Maximum: 599.

statusMessagestringOptional

A safe explanation suitable for display.

dataobjectRequired

No field description supplied.

401

A valid Developer API bearer token is required.

Response headers

WWW-AuthenticatestringOptional

Bearer authentication challenge. A rejected token can include the invalid_token error.

application/json

Uses the same response body schema as HTTP 400.

402

An active eligible Marketing entitlement is required.

application/json

Uses the same response body schema as HTTP 400.

403

The token scope, current Space role or plan allowance does not permit this operation.

application/json

Uses the same response body schema as HTTP 400.

404

The resource was not found in the token Space or the operation is unavailable.

application/json

Uses the same response body schema as HTTP 400.

429

The request rate limit was reached. Edge traffic limits can also return 429.

Response headers

RateLimit-LimitintegerOptional

Per-token capacity in the reported gateway window, expressed in requests of this operation. A shared Space budget also applies. Present when the request reaches the authenticated gateway. Minimum: 1.

RateLimit-RemainingintegerOptional

Requests of this operation remaining under the current token, Space and applicable operation-group quotas. Present when the request reaches the authenticated gateway. Minimum: 0.

RateLimit-ResetintegerOptional

Unix timestamp in seconds when the reported gateway quota resets. Present when the request reaches the authenticated gateway. Minimum: 0.

Retry-AfterintegerOptional

Seconds to wait before retrying, when the limiting policy supplies a retry time. Minimum: 1.

application/json

Uses the same response body schema as HTTP 400.

503

The operation is temporarily unavailable.

application/json

Uses the same response body schema as HTTP 400.

Was this helpful?