Does Express Work With Sanity?
Express and Sanity work together seamlessly—use Express as your backend API server and Sanity as your headless CMS, querying content via Sanity's APIs.
Quick Facts
How Express Works With Sanity
Express serves as an excellent backend layer for applications consuming Sanity content. Sanity provides a GraphQL API and REST endpoints that Express can query directly, making it straightforward to build custom endpoints that fetch, transform, and serve Sanity content to frontend clients. This architecture decouples your content management from your application logic—Sanity handles the CMS, Express handles business logic, caching, authentication, and custom endpoints.
The typical pattern involves installing the Sanity client library in your Express app and making requests to Sanity's Content Delivery API (for published content) or Content Management API (for draft/unpublished content). You can create middleware to cache responses, add request validation, implement webhooks for real-time content updates, and compose Sanity queries using GROQ (Sanity's query language). This gives you flexibility to shape data exactly as your frontend needs it without exposing Sanity credentials or query complexity to clients.
Developers appreciate this combination because Express remains lightweight and unopinionated while Sanity handles collaborative editing and structured content. You maintain full control over your API layer, can add authentication/authorization logic, and can even version your API independently from content changes.
Best Use Cases
Quick Setup
npm install express @sanity/client dotenvimport express from 'express';
import sanityClient from '@sanity/client';
import dotenv from 'dotenv';
dotenv.config();
const app = express();
const client = sanityClient({
projectId: process.env.SANITY_PROJECT_ID,
dataset: process.env.SANITY_DATASET,
apiVersion: '2024-01-01',
token: process.env.SANITY_TOKEN,
useCdn: true,
});
app.get('/api/posts', async (req, res) => {
try {
const posts = await client.fetch(
`*[_type == "post"] | order(publishedAt desc) [0...10] { _id, title, slug, publishedAt }`
);
res.json(posts);
} catch (error) {
res.status(500).json({ error: error.message });
}
});
app.listen(3000, () => console.log('Server running on :3000'));Known Issues & Gotchas
Sanity API rate limits can be hit if querying frequently without caching
Fix: Implement Express middleware with Redis or in-memory caching; use Sanity's CDN; batch requests where possible
Sanity token exposure if hardcoded in Express environment or leaked in responses
Fix: Always use environment variables for tokens; use read-only tokens for public APIs; never log or return tokens to clients
GROQ queries have a learning curve and error messages can be cryptic
Fix: Use Sanity's Vision tool to test queries; refer to GROQ documentation; start with simple queries and iterate
Express doesn't auto-refresh when Sanity content changes—requires webhooks or polling
Fix: Set up Sanity webhooks pointing to Express endpoints; use ISR (Incremental Static Regeneration) if paired with Next.js
Alternatives
- •Next.js API Routes + Sanity (tighter integration, built-in ISR, simpler setup for full-stack apps)
- •Fastify + Sanity (similar to Express but with better performance for high-throughput APIs)
- •Strapi + Express (self-hosted headless CMS alternative if you want full control over your CMS)
Resources
Related Compatibility Guides
Explore more compatibility guides