← Guides

Airtable API limits explained: 5 requests per second, monthly caps and 429 errors

Updated 2026-11-22. Sources are listed at the end.

Airtable limits its Web API in two ways: a rate limit per base and per user, and a monthly number of calls per Airtable workspace that depends on the plan.

Rate limits

  • 5 requests per second per base.
  • 50 requests per second for the traffic of one user's personal access tokens, across their bases.
  • Over the limit, Airtable answers 429, and you need to wait 30 seconds before the next request.

Monthly call caps

Monthly Web API calls per Airtable workspace
Airtable planCalls per monthOver the cap
Free1,000A one-time 30-day grace period, then calls over the cap are blocked until the month resets
Team100,000Calls slow to 2 requests per second until the month resets
Business, Enterprise ScaleNo monthly capRate limits per base still apply

Calls are counted per Airtable workspace for each calendar month (UTC) and reset on the first day of the month. Airtable's article also says that metadata and schema calls count, and that third-party integrations use the same monthly quota as your own scripts (read 21 November 2026).

How to stay under the limits

  • Read 100 records per call (pageSize=100, the maximum) and follow offset.
  • Pace requests below 5 per second per base, for example one request every 250 ms, and leave room for other integrations on the same base.
  • Handle 429 properly: wait at least 30 seconds, then retry once. Retrying immediately only extends the block.
  • Cache the schema instead of fetching it before every request.
  • Estimate before you schedule: calls per run are about (records รท 100) per table, plus schema calls. Multiply by runs per month and compare with your plan's cap.

A simple retry in a shell script:

STATUS=$(curl -s -o out.json -w '%{http_code}' -H "Authorization: Bearer $AIRTABLE_TOKEN" "$URL")
if [ "$STATUS" = "429" ]; then
  sleep 30
  STATUS=$(curl -s -o out.json -w '%{http_code}' -H "Authorization: Bearer $AIRTABLE_TOKEN" "$URL")
fi

For a full backup routine built on these limits, see how to back up an Airtable base.

Lindenkit Backup for Airtable: coming soon

We are building a scheduled backup of the Airtable bases you choose (records, attachments and schema) into a Cloudflare R2 bucket you own, using a token with read scopes only. It is not available yet and has no release date.

Read about it and join the waitlist

Sources