Flow · 6 steps

Serve your customer pages on your own domain

Have your customers open their quotes, orders, invoices and tracking on a subdomain of yours — orders.yourstore.com — instead of Manifold's address.

Add the subdomain, create the one CNAME record it answers at your DNS host, and Manifold issues and renews its certificate. Once it is live every new link and email uses it, and links already sent on Manifold's address move to it. If the record is ever removed, links fall back to Manifold's address and your owners are emailed; put it back and it switches by itself.

Services involved

A filled dot is a read; a ring is a call that changes something.

  • Notifications: https://notifications.getmanifold.io

Every call carries Authorization: Bearer $MANIFOLD_TOKEN unless its step says otherwise (getting a token). Run a flow in your sandbox, not your live organization: see Before you start.

1 Add your subdomain

Manifold registers it with its edge and answers the CNAME to create, and an optional TXT to prove the name first.

POST /settings/pages-domain Notifications

Request · application/json
{
  "hostname": "pages-host.ridgeline-outdoor.example"
}

What the answer holds: the operation's example.

From your answer, later steps send domain.hostname as {hostname}.

Records notifications.pages-domain-requested.

2 Check it once the record is in place

The edge finds the name routed to it, then its certificate issued: verified, then live. It is checked every ten minutes by itself too.

POST /settings/pages-domain/check Notifications

What the answer holds: the operation's example.

Records notifications.pages-domain-verified, notifications.pages-domain-live.

3 Read where it stands

Live, with the records to keep in place and the address your links use now.

GET /settings/pages-domain Notifications

What the answer holds: the operation's example.

4 The host your links name

What fulfillment asks when it answers a link: public, since every link a customer is sent prints it.

GET /brands/org_01a15a10-2b3c-7d4e-8f50-61728394a5b6/pages-host Notifications

What the answer holds: the operation's example.

5 Whose pages the host serves

What the customer pages ask of a request that arrives on your host.

GET /pages-hosts/{hostname} Notifications

What the answer holds: the operation's example.

6 Let it go

New links use Manifold's address again; the CNAME can then be deleted at your DNS host.

DELETE /settings/pages-domain Notifications

What the answer holds: the operation's example.

Records notifications.pages-domain-removed.

What a recorded fact is: Facts and the journal. Why a repeated step changes nothing: Idempotency and retries.