Custom domain support for Sanity API endpoints for white labeling

2 repliesLast updated: Nov 29, 2025

Hello everyone,
just a quick question/suggestion. Could you consider adding a custom domain support for the API ({id}.
api.sanity.io ) itself so companies could use it as a white label solution? Currently adding a CNAME for example would result in a mismatching domain error in the ssl certificate.
Thank you in advance, I really enjoy working with Sanity!
AI Update

Great question! I appreciate your enthusiasm for Sanity, and I understand the need for white-label solutions in enterprise contexts.

Unfortunately, custom domains for the Sanity API endpoints ({id}.api.sanity.io) are not currently available as a standard feature, even on Enterprise plans. The SSL certificate mismatch you're encountering when trying to use a CNAME is expected behavior since the certificates are issued for the *.api.sanity.io domain pattern.

However, there are a few things worth noting:

Current Enterprise Options:

Potential Workarounds:

Why This Matters:

For true white-label solutions, having custom domains across all touchpoints (including API endpoints) is important for brand consistency and client trust. This is a reasonable feature request, and Sanity's team is generally responsive to enterprise needs.

I'd suggest submitting this as a feature request through their community Slack or directly to your account team if you're already on an Enterprise plan. The more they hear about this use case, the more likely it could be prioritized!

Show original thread
2 replies

Was this answer helpful?

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Related contributions