
Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag storeYes, there is! Sanity has a Request Logs feature that can help you track down where those API requests are coming from.
If you're on a self-serve plan, you can access request logs directly from your project settings:
The logs come as GZIPPED NDJSON files that contain detailed information about every request.
The request logs include really useful fields like:
You can convert the compressed NDJSON to CSV for easier analysis:
gunzip --stdout [logfile].ndjson.gz | npx json2csv --ndjson --output [output].csvOr use tools like jq, GROQ CLI, or even upload samples to ChatGPT to help analyze patterns.
Requests from Sanity Studio are marked as studioRequest and don't count toward your API usage or cost. Make sure to filter these out when analyzing what's driving your actual API consumption.
Based on your situation with CDN enabled, check for:
requestType: "API" instead of "APICDN" (might indicate CDN isn't being used where you think it is)You might also want to implement request tags in your code going forward to make it easier to track which parts of your application are making which requests.
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.
Content operations
Content backend


The only platform powering content operations
By Industry


Tecovas strengthens their customer connections
Build and Share

Grab your gear: The official Sanity swag store
Read Grab your gear: The official Sanity swag store