Quick answer
The Google Sheets API limits requests to 60 reads per minute per user and 300 per minute per Google Cloud project. SheetZAPI sits in front of the Google Sheets API as a caching proxy: your app hits SheetZAPI's Redis-cached endpoints (sub-15ms), and SheetZAPI only calls Google when the cache expires. Thousands of app requests can be served from a single cached Google Sheets read.
As of 2024, the Google Sheets API v4 enforces: 60 requests per minute per user (read and write combined), 300 requests per minute per Google Cloud project, and 500 requests per 100 seconds per project. Exceeding these returns a 429 Too Many Requests error. For apps with more than a handful of users, these limits are easy to hit — especially for read-heavy dashboards or public-facing pages.
Every GET request through SheetZAPI is cached in Redis with a configurable TTL. Free and Hobbyist plans use a 60-second TTL. Developer plans configure TTL from 5 seconds to 24 hours. A cache hit never touches the Google Sheets API — it returns from Redis in under 15ms. This means 10,000 app requests per minute can be served from a single Google Sheets read every 60 seconds, staying well within Google's rate limits.
If your data changes infrequently (product catalog, FAQ list, price table), set a long TTL: 1 hour or more. Your users always get fast responses and you never hit Google's quota. If your data changes frequently (live inventory, real-time scores), set a shorter TTL (5-30 seconds) and SheetZAPI automatically fetches fresh data at the configured interval. You control the freshness-speed tradeoff per sheet.
Write operations (POST, PATCH, DELETE) always go through to Google Sheets immediately and invalidate the cache for that sheet. For high-write workloads (hundreds of writes per minute), consider batching writes or using a real database as the primary store with Google Sheets as a view. SheetZAPI's batch operations (Team plan) combine multiple writes into fewer Google Sheets API calls.
What is the Google Sheets API rate limit?
The Google Sheets API v4 limits read and write requests to 60 per minute per user and 300 per minute per Google Cloud project. Exceeding these returns a 429 error.
How do I avoid hitting Google Sheets API rate limits?
Use SheetZAPI. Its Redis caching layer serves repeated reads from cache without calling Google Sheets. Thousands of requests per minute can be served from a single cached Google Sheets read.
How fast are SheetZAPI cached responses?
Cache hits return in under 15ms. The cache is Redis-backed and served from the same region as your request.
Can I configure how often SheetZAPI refreshes data from Google Sheets?
Yes. On Developer plans and above, you set the cache TTL per sheet — from 5 seconds to 24 hours. Free and Hobbyist plans use a fixed 60-second TTL.
Stop hitting Google Sheets rate limits — start caching
Get Started Free