Runs onWrit Cloud
On this page
Your endpoints, your host.
Serve your published endpoints from your own domain, with DNS verification and automatic TLS. The routing stays /v1/{slug}/{path}, and your callers keep the same csk_ consumer keys.
host ▸ the only change
Only the host changes.
https://api.usewrit.app/v1/acme/price-check
https://api.yourcompany.com/v1/acme/price-check
The route stays /v1/{slug}/{path} and auth stays the caller’s csk_ consumer key. Callers change the base URL — nothing else.
The gateway resolves your tenant per request from the Host header: a verified custom domain, the built-in {slug}.api.usewrit.app subdomain, or the shared host with the slug in the path. All three answer the same routes.
setup ▸ four steps
Four steps to a branded host.
- 01Add your domain
Enter the host you want to serve endpoints from, e.g. api.yourcompany.com.
- 02Add the DNS records
Create the CNAME and TXT records Writ shows you in your DNS provider.
- 03Verify ownership
Writ checks the TXT record and confirms the domain is yours.
- 04TLS goes live
A certificate is issued automatically and traffic starts flowing.
; Verify ownership and route traffic to Writ
api.yourcompany.com. CNAME endpoints.usewrit.app.
_writ-verify.api.yourcompany.com. TXT "writ-verify-3f9Kq2xR7mVzT1pLbN8wYc4AeJ6dHs0U" Add both records in your DNS provider. The CNAME routes traffic; the TXT proves ownership once.
faq
Questions, answered.
How do I verify a domain?
Does anything else change?
Which plans include custom domains?
Is this required to expose an API?
go ▸ brand it
Serve from your own domain.
Add a host, drop in two DNS records, and ship endpoints under your brand.