Airtable API Limits in 2026: Rate Limits, Monthly Caps, and Plan Differences
Every Airtable plan shares the same rate limit: 5 requests per second per base. That limit does not change whether you are on Free or Enterprise. What does change is the monthly cap on total API calls: Free is capped at 1,000 and Team at 100,000, while Business and Enterprise have unlimited monthly API calls. For developers building applications on top of Airtable, understanding these limits is critical because hitting either constraint means your application stops working. This page covers both limits, practical consumption models, 429 error handling strategies, and the effective cost per API call by plan.
API Limits by Plan
Free
1,000
calls/mo (~33/day)
Team
100,000
calls/mo (~3,333/day)
Business
Unlimited
calls/mo (5 req/sec/base)
Enterprise
Unlimited
calls/mo (5 req/sec/base)
All plans: 5 requests per second per base. This rate limit cannot be increased.
Handling 429 (Too Many Requests) Errors
When you exceed 5 requests per second to a single base, Airtable returns a 429 status code. The response includes a Retry-After header indicating how many seconds to wait before retrying. Your application must handle this gracefully to avoid data loss or user-facing errors.
Recommended: Exponential backoff with jitter
1st retry: wait 1 second + random 0-500ms
2nd retry: wait 2 seconds + random 0-500ms
3rd retry: wait 4 seconds + random 0-500ms
4th retry: wait 8 seconds + random 0-500ms
Max wait: 30 seconds, then fail with error
Batch your API requests to reduce the total number of calls. Airtable allows up to 10 records per create or update request. Instead of 100 individual create calls (taking 20 seconds at rate limit), batch into 10 calls with 10 records each (taking 2 seconds). This is the single most effective optimization for API-heavy applications.
Monthly Cap Consumption Models
How quickly different application patterns consume the monthly API call allowance.
Light dashboard sync (every 15 min)
5,760 calls/moFree insufficient, Team works
A dashboard that fetches updated records from 2 tables every 15 minutes during business hours (8 AM to 8 PM). Each sync requires 2 API calls: list records for each table. At 16 hours/day with 4 syncs/hour per table, this generates 192 calls/day or 5,760/month.
Active sync app (every 5 min)
17,280 calls/moTeam works
An application that syncs data between Airtable and an external system every 5 minutes. Each sync checks for updates and pushes changes, requiring approximately 4 API calls per cycle. Running 24/7, this generates 576 calls/day or 17,280/month.
Customer portal (real-time reads)
60,000 calls/moTeam works
A customer-facing portal where each page load fetches data from Airtable. At 200 unique visitors per day averaging 10 API calls per session (list records, get record details, check permissions), this generates 2,000 calls/day or 60,000/month.
High-frequency data pipeline
432,000 calls/moNeeds Business plan (unlimited calls)
An automated data pipeline that syncs records every minute with 10 API calls per sync (list, filter, update, log). Running 24/7 at 10 calls/minute, this generates 14,400 calls/day or 432,000/month. Exceeds Team's 100,000 limit in just 7 days. Business and Enterprise have unlimited monthly API calls.
Webhooks vs Polling: Reducing API Consumption
Polling (checking for updates on a schedule) is the most common way applications interact with Airtable, but it wastes API calls when no changes exist. Airtable supports webhooks that notify your application when records change, eliminating the need for constant polling.
Polling (wasteful)
Checking every 5 minutes regardless of changes: 288 calls/day per table. With 5 tables, that is 1,440 calls/day or 43,200/month. Most calls return no new data, consuming quota for nothing.
Webhooks (efficient)
Airtable pushes change notifications to your endpoint. You only make API calls when data actually changes. Typical reduction: 60-90% fewer API calls depending on change frequency. Setup requires a publicly accessible webhook URL.
Effective Cost per API Call
| Plan | Price (1 seat) | Monthly Calls | Cost/Call |
|---|---|---|---|
| Free | $0 | 1,000 | $0.0000 |
| Team | $20/mo | 100,000 | $0.0002 |
| Business | $45/mo | Unlimited | N/A |
| Enterprise | ~$80/mo | Unlimited | N/A |
Cost per call calculated as plan price divided by API call allowance for a single-seat account. Multi-seat accounts share the same call allowance, increasing effective cost per call.
Frequently Asked Questions
What is Airtable's API rate limit?
Airtable allows 5 requests per second per base on all plans. Exceeding this triggers a 429 (Too Many Requests) error. The rate limit applies per base, not per account, so multiple bases can each handle 5 req/sec independently. Monthly API call caps: Free 1,000, Team 100,000. Business and Enterprise have unlimited monthly API calls.
How do I handle Airtable 429 errors?
Implement exponential backoff: wait 1 second after the first 429, then 2 seconds, then 4 seconds, up to a maximum of 30 seconds. Airtable's 429 response includes a Retry-After header indicating how long to wait. Batch your requests (up to 10 records per create/update call) to reduce total request count. Use webhooks instead of polling where possible.
How much does each Airtable API call cost?
On the Team plan ($20/seat/month with 100,000 calls), each API call costs approximately $0.0002 for a single-seat account. Business and Enterprise plans include unlimited API calls, so there is no meaningful per-call cost beyond the plan price. API calls are included in your plan; there are no per-call charges.
Can I increase Airtable's API rate limit?
The 5 requests per second per base limit cannot be increased on any plan, including Enterprise. However, you can work around it by distributing data across multiple bases (each gets its own 5 req/sec), batching records (up to 10 per request), and using field-specific returns to reduce payload size. Business and Enterprise already have unlimited monthly call volumes.