Content API

A Sanity-compatible HTTP API

@sanity/client, next-sanity and the Studio connect unmodified. Same routes, same request shapes, same response envelopes, served from /api of your own deployment.

shipped

The compatibility claim is the product. @sanity/client is configured with your deployment's URL and nothing else changes: queries, mutations, actions, listeners, uploads and the management-plane calls the Studio makes on boot are all served.

Handlers are pure (Request, ctx) => Promise<Response> functions with no framework in them, so the same API could be mounted outside Next.js without being rewritten.