What we do
Tools
Industries
Department
How we workLet's talk →
Home/Airtable/Airtable API
Airtable

The Airtable API: A First Request, the Call Budget, and Webhooks

Airtable's REST API reads and writes records in any base your token can reach, and its webhooks tell you when something changed. The first call takes ten minutes. What catches people later is the metering: a per-second limit on every base, plus a monthly call allowance on the Free and Team plans.

Your first request

Make a personal access token in Airtable's Builder Hub. Give it the scopes it needs (for example data.records:read and data.records:write) and add only the bases it should touch.

airtable.com/create/tokens Create token

Find the base ID. It's the part of the base URL that starts with app. Tables can be addressed by name or by their ID, which starts with tbl and survives renames.

Call it: GET https://api.airtable.com/v0/{baseId}/{table} with Authorization: Bearer <token>. You get up to 100 records and an offset to fetch the next page.

What a simple sync costs in API calls

Airtable counts calls per workspace per month on Free and Team. Polling is where the budget goes.

Example: one workspace on the Team plan, keeping three tables in step with an order system for a 30-day month.
Team plan monthly allowance 100,000
Checking 3 tables for changes every 5 minutes (3 × 12 an hour × 24 × 30) −25,920
Writing 400 changed records a day, 10 per request (40 requests a day) −1,200
Paging through a 6,000-record table each night (60 pages of 100) −1,800
Left for everything else in the workspace 71,080

The same job on the Free plan, with its 1,000 calls a month, runs out in under two days. Business and Enterprise Scale have no monthly cap, but the 5-requests-a-second limit per base still applies.

Airtable API errors and surprises

429 Too Many Requests

How you'll know: A backfill or parallel job fails after a burst of calls.

Fix: Each base takes 5 requests a second, and all traffic from one user's tokens shares 50 a second. After a 429 you have to wait 30 seconds. Pace requests below the limit rather than retrying straight away. Airtable's official JavaScript client backs off for you.

Writes are slow and burn calls

How you'll know: Updating 500 records takes 500 requests.

Fix: Create and update endpoints take up to 10 records per request. Batch them, and use performUpsert with fieldsToMergeOn so one call creates new records and updates existing ones by a key field.

An update wiped out other fields

How you'll know: After a sync, fields you never sent are blank.

Fix: You used PUT, which clears every field you leave out. Use PATCH to change only the fields in the request.

Select fields reject new values

How you'll know: A value that isn't already an option fails the write.

Fix: typecast is off by default. Set typecast: true to let Airtable convert strings and add select options, or map values to the existing options before sending.

Webhooks went quiet after a week

How you'll know: Change notifications stopped, though nothing was turned off.

Fix: Webhooks made with a personal access token or OAuth expire after 7 days. Calling refresh, or listing payloads, extends them another 7. Build that refresh into the job.

Polling on a timer, or listening for webhooks

Polling

Ask every few minutes

  • Simple to write: list records modified since the last check.
  • Costs calls whether or not anything changed.
  • Fine on Business plans, expensive on Free and Team.
Webhooks

Airtable tells you

  • The ping carries no data. You call list payloads to see what changed.
  • Each payload has a sequence number, so you can skip ones already handled.
  • Needs a public endpoint, a 7-day refresh, and a check if pings fail 13 times and notifications switch off.

For anything that runs all month, webhooks plus a nightly check is cheaper and closer to real time. Polling is for prototypes and Business-plan bases.

Making a sync you can stop thinking about

A sync that holds up treats every write as safe to repeat. Upsert on a key field instead of creating blindly, store the Airtable record ID next to the other system's ID, and keep a log of which webhook payloads were processed. Then a retry after a timeout updates a record instead of duplicating it.

It also needs someone watching for the slow failures: a token whose scopes changed, a field someone renamed in the base, a webhook that expired over a holiday. n-frames builds and runs Airtable API syncs with those checks built in, linking bases to order, inventory and CRM systems, and to other bases. For logic that can live inside the base, compare Airtable automations first.

Questions people ask

Does Airtable have a public API?

Yes. A REST API for records, plus metadata endpoints for bases, tables and fields, and a webhooks API that reports changes in a base.

Do I need an API key to use the Airtable API?

Not any more. Airtable replaced account-wide API keys with personal access tokens, which you scope to specific permissions and bases. Public integrations use OAuth instead.

Are there limits on how much I can do with the Airtable API?

Two kinds. Rate limits: 5 requests a second per base, and 50 a second across one user's tokens. Monthly limits per workspace: 1,000 calls on Free and 100,000 on Team, after which Team is throttled to 2 requests a second. Business and Enterprise Scale have no monthly cap.

Can non-developers use the Airtable API?

Through tools like Zapier or Make, which call it for you, yes, for simple jobs. A sync that batches writes, upserts on a key field and refreshes its webhooks every week takes a developer, or a team like n-frames that builds and maintains it for you.

Does Airtable support webhooks?

Yes. You create a webhook on a base and Airtable pings your URL when something changes. The ping is only a notice, so your code then lists the payloads to see the changes. Webhooks made with tokens expire after 7 days unless refreshed.

How many records can I create in one Airtable API request?

Up to 10 per create or update request. Reading returns up to 100 records per page, with an offset for the next page.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.