TL;DR
- Airtable turned off its old API keys on 1 February 2024, so there is no key left to find.
- Make a personal access token instead: profile menu, Builder hub, Developers, Personal access tokens, then Create token. Once you are signed in, airtable.com/create/tokens takes you there directly.
- Airtable shows a new token one time only. Copy it right away.
- Add to CRM connects with an Airtable sign-in, so it needs no token at all.
API keys no longer exist, so your Airtable API token is a personal access token, made in Builder hub. Open the profile menu, click Builder hub, choose Personal access tokens under Developers, and create a token with only the scopes and bases it needs. If you searched for the Airtable developer hub, this is the place: one Airtable help page uses that name, but the menu item says Builder hub.
Only want to connect Add to CRM? Skip the token. It signs in through Airtable itself, so there is nothing to paste.
The arrow marks Builder hub in the profile menu. Scroll the menu if you cannot see it.
On this page
Airtable API keys no longer work
Airtable began retiring user API keys on 18 January 2023 and finished on 1 February 2024. An old key in a script now gets nothing from the API. If that script sends the key as an api_key part of the web address, change that too, because Airtable does not support tokens sent that way.
Airtable's own advice is a personal access token for your own work and OAuth for an app that other people connect to. This page covers the token. Airtable's help and developer pages were checked in October 2026. The screenshots are older, so your screen may differ.
Create a personal access token
A personal access token is for your own use: an integration for yourself, your client or your company. It acts as your user account, so keep it secret. Airtable's developer guide walks through the same steps.
Open Builder hub. On your Airtable home screen, click the profile icon in the upper right corner, then click Builder hub. The menu can run long, so scroll down if the item is missing.
Find Personal access tokens. In the menu on the left, open Developers and click Personal access tokens.
Start a new token. On the token list, click the blue Create token button. In October 2026 Airtable's developer guide calls it Create new token, while its help page and our screenshot say Create token.
Name it. Pick a name you will recognise later. Airtable shows it in a record's revision history.
Check the scopes. The new form may already list four scopes:
data.records:read,data.records:write,data.recordComments:readanddata.recordComments:write. Our screenshot shows an X beside each one, so remove any the token does not need. Click Add a scope for anything missing. The next section explains them.Add a base. Under access, click Add a base and pick a base or a whole workspace. The token works only where you add it.
Create the token and copy it. Our screen shows a Create token button in the form's bottom right corner. Click it, and Airtable opens a box that says "Your token has been created" and that the token will only be shown once. Copy the token, store it somewhere safe, then click Done.
Which scopes to pick
A scope is a permission. Give the token the fewest your job needs. These are the main ones from Airtable's scope list, which has more, nearly all of them for Enterprise accounts.
| Scope | What it lets the token do |
|---|---|
data.records:read |
See the data in records |
data.records:write |
Create, edit and delete records |
schema.bases:read |
See the structure of a base, such as table names or field types |
schema.bases:write |
Edit the structure of a base, such as adding fields or tables |
data.recordComments:read |
See comments in records |
data.recordComments:write |
Create, edit and delete record comments |
workspacesAndBases:read |
View details about workspaces, bases and views, including collaborators |
webhook:manage |
View, create and delete webhooks for a base, and fetch their payloads |
user.email:read |
See the user's email address |
Each API call names the scope it needs on its page. Listing or getting records takes data.records:read. Creating and updating records both take data.records:write. Listing the bases a token can see, or reading the tables and fields inside a base, takes schema.bases:read. Creating a field takes schema.bases:write, and that call's page also asks for the Base creator role.
So a script that reads contacts, adds new ones and checks field names needs three scopes: data.records:read, data.records:write and schema.bases:read.
Choose the bases
The scope says what a token can do. The bases you add say where. A token works only in the bases and workspaces you give it, which can be any mix of them or everything under your account. The narrowest useful token is one scope on one base, and the picker lets you search by base ID as well as by name.
A token also never goes beyond the person who made it. To update a record, you need editor access to that base, and the token needs the scope too.
One limit catches people out: you cannot lock a token to one table or one view. It reaches every table in a base it can access, within the limits of its scopes. If a table holds data a tool should not see, our advice is to keep that table in a separate base. If you need to limit what a token can change, Airtable's route is field and table editing permissions, which API requests honour.
To check what a token can see, send a GET request to https://api.airtable.com/v0/meta/bases. It lists the bases the token can reach and needs the schema.bases:read scope.
Lost it? Regenerate or delete
Airtable does not keep the token text, so you cannot look it up later. If you lose it, regenerate the token and copy the whole new value.
- Go to airtable.com/create/tokens.
- Click the "..." icon beside the token.
- Click Regenerate token or Delete token.
Regenerating shows a warning first. The old string stops working, the name and permissions stay as they were, and every tool that used the old string needs the new one. Deleting asks you to confirm, and after that every request with the token is rejected. You can tick several tokens and delete them together.
To change a token's name, scopes or bases, click its name, or click "..." and then Edit token, and finish with Save changes.
By default a token has no expiry of its own. It stays active until you delete or regenerate it, though an Enterprise admin can set a lifetime cap. Webhooks are different: ones made with a token expire after 7 days unless you refresh them.
Use the token in a request
Put the token in the HTTP Authorization header, labelled Bearer, and use HTTPS for every call. A request that lists records looks like this:
GET https://api.airtable.com/v0/{baseId}/{tableIdOrName}
Authorization: Bearer YOUR_TOKEN
Table names and table IDs both work in that spot, but Airtable recommends IDs, so a renamed table does not break your request. Both IDs sit in the address bar while a base is open. In the example https://airtable.com/appeqX9XTkHZNfSbn/tbl99vKzVh7NwLwm8/ from Airtable's guide to finding IDs, appeqX9XTkHZNfSbn is the base ID and tbl99vKzVh7NwLwm8 is the table ID, which starts with tbl.
Want the API reference for your own base? On a laptop or desktop, open the Help button in the base's upper right corner, then pick the API documentation link at the foot of the list.
Two errors tell you most of what you need. A 401 means Airtable rejected the token, so it may be mistyped, deleted or no longer valid. A 403 usually means the token lacks a scope or a base, you lack permission in that base, or an ID is wrong. The usual message begins "Invalid permissions, or the requested model was not found" and goes on to ask you to check that both your user and your token have the required permissions. Check the scopes and bases first.
Airtable API limits
The API allows 5 requests per second per base. Airtable's getting-started article adds that every plan gets the same limit and that higher limits are not currently available. A second ceiling of 50 requests per second covers all traffic from one user's tokens, or one service account's. Go over a limit and you get a 429 error and must wait 30 seconds, so build in a back-off and retry.
Three habits keep you under the line. Send up to 10 records in one request. Read in pages, since Airtable returns up to 100 records at a time. And for heavy reading, put a caching proxy in front, as Airtable recommends.
Plans also carry a monthly cap. Airtable's call-limits page lists 1,000 API calls per workspace per month on the Free plan and 100,000 per workspace per month on the Team plan. Airtable's pages disagree about what a Team workspace sees after passing the cap, so read the call-limits page for your own plan before you build anything that depends on it.
Token or sign-in? What Add to CRM uses
Airtable draws the line itself. A personal access token is for personal development. Any integration that lets other people grant access to Airtable should use OAuth, where the developer picks the scopes and each user decides which resources to share.
Add to CRM takes the OAuth side, which you see as a normal sign-in with Airtable. You set it up in the Add to CRM web app, not in the extension, and your credentials are stored encrypted on our servers.
So a tool that asks you to paste a personal access token deserves a second look. Airtable's guidance, and its token form in our screenshot, say to use the token only for your own development and not to share it with third-party services.
Connect Airtable
Sign in with Airtable. No API key needed.
Airtable Chrome extensionConnect Airtable to Add to CRM
Add to CRM is a Chrome extension that finds verified contact details and adds a person to your Airtable base in one click. It works from LinkedIn, Gmail and Outlook, and each contact is enriched with 20+ data points. A credit is used only when contact details are found. Start from the Add to CRM Airtable page, then:
- Open the Connect step in the Add to CRM web app and choose Airtable.
- Click Continue to Airtable and approve access on Airtable's screen.
- Back in Add to CRM, the screen lists the bases you shared and can write to, under Which base should we use? Pick the one that should receive your contacts and click Continue.
Your first 7 days are a free trial. A card is required, and you can cancel any time. For plans, see pricing.
More Airtable guides: how to use Airtable as a CRM, how to import contacts into Airtable and how to export contacts from Airtable. For other CRMs you can connect, browse the full integrations list.
FAQ
Is my old Airtable API key still valid?
No. Airtable ended API keys on 1 February 2024. Use a personal access token, or OAuth for an app other people connect to.
Does a personal access token expire?
Not by default. It stays active until you delete or regenerate it, though an Enterprise admin can set a lifetime cap.
Can I limit a token to one table?
No. Access is set per base or workspace, and a token can reach any table in a base it can access, within its scopes. Limit it by base instead.
Which Airtable plan do I need?
Personal access tokens come with all plan types. What changes by plan is mainly the monthly call limit, and a few scopes are Enterprise-only.