# Caching a Google Sheets JSON API A spreadsheet was never built to be a high-traffic API. A cache in front of it is what makes the difference — fast reads, fewer calls to Google, and resilience when your traffic spikes. *Last updated: 2026-07-11 · Source: * ## Key facts - The Google Sheets API allows **300 read requests per minute per project** and **60 per minute per user**. Past that it returns `429 RESOURCE_EXHAUSTED`. ([source](https://developers.google.com/workspace/sheets/api/limits)) - A cached endpoint reads the sheet **once per TTL**, not once per request — so 10,000 visitors become one upstream read, and Google's quota stops being your problem. - PasteSheet's TTL is a fixed **5 minutes on Free** and a configurable **30 seconds to 1 hour** on paid plans, served stale-while-revalidate so an expiring cache never blocks a request. - A manual refresh re-reads the sheet immediately and **does not count against your monthly request quota** — so "I need it fresh right now" never costs you anything. ## Why cache a sheet at all Reading a Google Sheet directly on every request is slow and burns through [rate limits](https://pastesheet.com/guides/google-sheets-api-rate-limits). Caching stores the fetched rows for a short window and serves them from a fast layer, so repeated reads never touch Google. For read-heavy content — listings, config, FAQs — nearly every request can be a cache hit. ## What caching buys you - Speed — responses served in milliseconds, not a round-trip to Google. - Fewer API calls — one cached fetch serves many visitors. - Resilience — a traffic spike does not multiply into rate-limit errors. - Stability — brief Google hiccups are hidden behind the cache. ## How PasteSheet caches Every endpoint sits behind an edge cache with a TTL you control — a fixed 5 minutes on Free, or a custom 30-second to 1-hour window on paid plans. Reads are served stale-while-revalidate, so an expiring cache never blocks a request, and you can force a manual refresh the instant the sheet changes. Manual refreshes do not count against your [monthly quota](https://pastesheet.com/pricing). The result behaves like a CDN in front of your spreadsheet. Learn the fuller picture in [using Google Sheets as a REST API](https://pastesheet.com/guides/google-sheets-rest-api). ## Frequently asked questions ### Should I cache a Google Sheets API? Yes, for anything read-heavy. Caching serves repeated reads from a fast layer instead of calling Google every time, which is faster and avoids rate limits. PasteSheet caches every endpoint by default. ### How long is data cached? PasteSheet uses a fixed 5-minute TTL on Free and a configurable 30-second to 1-hour TTL on paid plans, with stale-while-revalidate so an expiring cache never blocks a request. ### How do I get fresh data immediately? Trigger a manual refresh, which re-fetches the sheet right away and does not count against your monthly request quota. Otherwise edits appear after the cache TTL expires. ## Sources - [Usage limits — Google Sheets API](https://developers.google.com/workspace/sheets/api/limits) — Google ## Related guides - [Google Sheets API Rate Limits (60/min)](https://pastesheet.com/guides/google-sheets-api-rate-limits) — Google Sheets API rate limits are 300 reads per minute per project and 60 per user. Here is why read-heavy apps hit a 429 — and how caching removes the wall. - [Turn Google Sheets Into a REST API (No Code)](https://pastesheet.com/guides/google-sheets-rest-api) — Turn a public or restricted Google Sheet into a live JSON REST API with filtering, sorting, and pagination — no backend, no code. - [Fix Google Sheets API Quota Exceeded (429)](https://pastesheet.com/guides/google-sheets-api-quota-exceeded) — Seeing RESOURCE_EXHAUSTED or a 429 from the Google Sheets API? Here is the per-minute quota, why you hit it, and how caching removes it for read-heavy apps. --- [PasteSheet](https://pastesheet.com) turns any Google Sheet into a live REST API and MCP server for AI agents — no backend, no code. Canonical HTML version of this page: