Add or reassign a subdomain
Maps a managed subdomain ({name}.run402.com) to a site deployment. The target is resolved server-side from whatever the caller holds: deployment_id (a legacy dpl_ id, or a rel_ / op_ id from a unified-apply commit), release_id, or neither — then the project's live (active) release. A release with no site files (a functions-only API) binds to the project's empty deployment; the host serves the live release's routes. 404 when the named release or operation is not this project's, or the project has never deployed. A first activation that serves site files or routes and has no subdomains slice claims a host automatically (derived from the project name); this route is for choosing a different name or claiming after the fact.
Request
- Base URL: https://api.run402.com
- URL: https://api.run402.com/subdomains/v1
- Auth: HTTP bearer
Request body
Response
Subdomain created
Example response
{
"project_id": "prj_1741340000_0042"
}Changes
No recorded changes to this operation across all 1 revision of this API.