Domains

Serve a site on a domain of its own.

Attach a domain

A site can answer on its own domain as well as its manifestx.ai address. You attach the domain, the domain's owner adds a DNS record at their DNS provider, and the HTTPS certificate is issued automatically. Manifest doesn't register or sell domains.

curl -X POST https://api.manifestx.dev/v1/projects/proj_…/domains \
  -H "Authorization: Bearer $MANIFEST_ACCOUNT_KEY" \
  -H "Idempotency-Key: domain-site_8231-docs" \
  -H "Content-Type: application/json" \
  -d '{ "hostname": "docs.acme.com", "env": "production", "validation": "http" }'

A new domain answers 201 Created with the DNS records to add:

{
  "domain": {
    "hostname": "docs.acme.com",
    "requested": "docs.acme.com",
    "env": "production",
    "validation": "http",
    "status": "pending",
    "certificate_status": "pending_validation"
  },
  "records": [
    { "purpose": "Point the domain to the site", "type": "CNAME", "name": "docs", "value": "cname.manifestx.ai" }
  ],
  "root_redirect": null,
  "request_id": "…"
}

name is the label to type into the DNS provider's Name/Host field, which adds the domain itself. These are the same records the Manifest connector gives for the same domain.

• Root domains. A root such as acme.com is served at www.acme.com (domain.hostname), because most DNS providers can't put a CNAME on a root. root_redirect then describes the forwarding to set up at the registrar so acme.com goes to https://www.acme.com.
• Moving a live domain. With "validation": "txt", records starts with a TXT record. Add only that one first: the certificate is issued while the old site keeps serving. Add the CNAME once the status shows the certificate active, and traffic moves with HTTPS on both sides.

Sending the same hostname again updates it in place (for example, to switch validation) and answers 200. A hostname already attached to another project is refused.

Check status

curl https://api.manifestx.dev/v1/projects/proj_…/domains/docs.acme.com \
  -H "Authorization: Bearer $MANIFEST_ACCOUNT_KEY"

{
  "domain": {
    "hostname": "docs.acme.com",
    "env": "production",
    "status": "pending",
    "hostname_status": "pending",
    "certificate_status": "pending_validation",
    "certificate_validation": { "method": "http", "expected_records": [], "errors": [] }
  },
  "request_id": "…"
}

status is one of:

hostname_status and certificate_status are the underlying states; certificate_validation appears until the certificate is active and lists what is still expected. Poll every minute or so while status is pending. The domain serves the site from the first check that reads active. After that, a later error (for example a certificate renewal that timed out, or the CNAME removed) is reported but doesn't take the site off the domain; fix the records and attach again. The exception is a domain whose hostname_status reads deleted: it has no certificate or routing left, so it stops serving. Attaching it again issues a new certificate, and the domain reads pending until it validates.

Remove a domain

curl -X DELETE https://api.manifestx.dev/v1/projects/proj_…/domains/docs.acme.com \
  -H "Authorization: Bearer $MANIFEST_ACCOUNT_KEY"

Answers { "removed": "docs.acme.com", "request_id": "…" }. The site stops answering on that domain at once and the domain is free to attach elsewhere. The CNAME can then be deleted at the DNS provider.

Errors