Add
Add a custom domain to a project environment (production by default) and get the CNAME record to create.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The organization's id (UUID) or slug — either form is accepted.
The project's id (UUID) or slug — either form is accepted.
Body
Hostname you control, e.g. "app.acme.com".
^(?:[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?\.)+[a-z]{2,}$Environment the domain routes to. Defaults to "production". An environment that does not exist on the project answers 404. The preview environment answers 422: preview apps are ephemeral per-pull-request deployments, so a stable hostname can never attach to them.
^[a-z][a-z0-9-]{0,38}$Response
Domain registered. Create the CNAME from the instructions, then check the domain until it goes active.
^(?:[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?\.)+[a-z]{2,}$Slug of the environment this domain routes to.
^[a-z][a-z0-9-]{0,38}$Verification state: pending_dns until the CNAME points at the platform, pending_ssl while the certificate is issued, then active. failed is terminal.
pending_dns, pending_ssl, active, failed Why verification is stuck, when the edge reported a reason.
DNS setup step. Production domains target the project's managed subdomain, e.g. "CNAME app.acme.com → my-app.korve.app"; domains on other environments target that environment's own subdomain, e.g. "CNAME staging.acme.com → my-app-staging.korve.app".