Custom Domain
Configure Custom Domain
Set the Web Frontend and OIDC Backend hosts for an app.
PUT
Sets the two custom hosts and starts provisioning. Returns the
CustomDomainStateDto, including the DNS records to add. See Custom Domain for the concept and lifecycle.
Request
Bearer <API_KEY> from Console > Developers > Workspace API Keys.application/jsonPath parameters
Client identifier of the app.
Request body
The Web Frontend host (serves the hosted verification UI), e.g.
verify.example.com. Host only — no scheme or path.The OIDC Backend host (serves the OIDC endpoints), e.g.
connect.example.com. Host only — no scheme or path.Response
Returns the updatedCustomDomainStateDto. After a successful configure, the status moves to awaiting_dns and the response carries the DNS records to add.
The configured Web Frontend host.
The configured OIDC Backend host.
Lifecycle status. One of
unconfigured, awaiting_dns, verifying, active, invalid.What you need to do next. One of
none, add_cname, waiting, verify, contact_support, retry.Human-readable explanation of the current status. Omitted when there is nothing to report.
DNS records to add at your DNS provider. See Get Custom Domain for each record’s fields.
ISO 8601 timestamp of the most recent verify. Omitted until the first verify runs.
Configuring only generates the records — it does not verify them. Add all returned DNS records, then call Verify Custom Domain to advance the status.

