Headless commerce
Warm product and inventory JSON routes before storefront traffic.
← Back to features
Feature
API Warmers
Keep JSON and HTTP API endpoints hot the same way you warm pages.
APIs get cold too. API warmers let you schedule authenticated or public HTTP calls—GET, POST, and more—with headers, cookies, optional bodies, and combination matrices so cached API responses stay fresh for clients and backends.
Highlights
- Warm non-HTML HTTP endpoints on a schedule
- Custom methods, headers, cookies, and bodies
- Config matrices for variants and environments
- OpenAPI import on supported plans
Built for headless and service caches
Headless storefronts, BFF layers, and shared data APIs often sit behind CDN or gateway caches. API warmers hit those routes like real clients so the next consumer request is served warm.
Variants without duplicate warmers
Config matrices expand combinations of headers, query params, or bodies so you can cover locales, tenants, or feature flags without maintaining dozens of nearly identical warmers.
How it works
- 1
Define endpoints
Add URLs, methods, and auth-related headers or cookies.
- 2
Expand variants
Use matrices or OpenAPI import where available.
- 3
Schedule & monitor
Run on interval and watch results alongside website warmers.
Where it shines
Public developer APIs
Keep documentation demos and popular endpoints responsive.
Internal BFFs
Prewarm aggregated endpoints used by mobile or web clients.
Frequently asked questions
- Are API warmers separate from website warmers?
- Yes. They have their own limits on plans and are managed under API Warmers in your account.
- Can I send request bodies?
- On plans that allow API request bodies, yes—useful for POST-heavy APIs.
Related features
All featuresReady to try this in your account?
Create a free Cache Rocket account, verify a hostname, and turn this capability on for your site or API.