Help for owners
My Airtable connection stopped working after the API key change
Short answer
Airtable began retiring user API keys on January 18, 2023 and finished on February 1, 2024, after which keys can no longer access the API. Integrations now need a personal access token with the right scopes and bases, or OAuth for third-party apps. The fix is replacing the key, not retrying.
Does this sound like your situation?
- A script, website form or tool that read Airtable stopped working.
- The error mentions authentication, an invalid key or a missing permission.
- It was built by someone who has left and nobody knows where the key is used.
- A new token exists but it still cannot see my base or cannot create fields.
- A no-code tool shows its Airtable connection as broken.
Why does this happen?
User API keys were switched off
Airtable began deprecating user API keys on January 18, 2023 and completed the process on February 1, 2024. Under that change, API keys can no longer access the Airtable API.
Confirmed by support.airtable.com
Tokens are limited to bases and scopes
A personal access token can be restricted to specific bases or workspaces, and scopes control which endpoints it can use. A token never does more than the person who created it is allowed to do in that base, so a token made by a user with limited access will fail on other bases.
Confirmed by support.airtable.com
Some actions need extra scope and base access
For example, creating fields needs the schema write scope and the base must also be added as a resource on the token. A token with only data scopes will fail there.
Confirmed by support.airtable.com
Third-party apps should use OAuth
Airtable recommends personal access tokens for individual use and OAuth for third-party integrations. A tool that stored your old key needs to be reconnected.
Confirmed by support.airtable.com
The token is tied to a person
If the token was created by an employee who later loses access, the integration stops with them. That is a handover problem, not an Airtable fault.
What can I do about it today?
- List everything that talks to AirtableWebsite forms, scripts, no-code tools, reporting tools. Ask who set each one up.
- Do not paste tokens in email or chatA token is a password. Share it only through a password manager.
- Reconnect no-code tools through their own screenUse the tool's Airtable connection step and sign in again, which sets up the permission for you.
- Create tokens from an account that will stayUse a named owner account, not a personal one that may leave. Give the token only the bases it needs.
- Keep the old setup untouchedDo not delete scripts or automations. Replace the credential and test with one record.
When should I bring someone in?
- Code you do not have the source for reads or writes the base.
- Customer-facing forms or orders depend on the connection.
- You are unsure which scopes a token needs.
How do I handle it?
- Find every callerI search the code, settings and tools for each place that uses Airtable, so no integration is left on the old key.
- Pick the right credential typePersonal access tokens for your own internal tools, OAuth where the tool belongs to someone else.
- Give the minimum scopesEach token gets only the scopes and bases the integration needs.
- Store the secret safelyTokens go into the server's secret settings, never into code or a spreadsheet.
- Test on a copyI test reads and writes on a copy of the base, then switch the live one.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can I get my old API key back?
No. Airtable states that API keys can no longer access the Airtable API, so a token or OAuth is needed.
Do webhooks made with an API key still work?
Airtable states that webhooks created with user API keys do not expire, but new ones cannot be created that way.
Is one token enough for all my tools?
It is safer to have one per tool, limited to the bases it uses, so that you can revoke one without breaking the others.
Who should own the token?
An account the company controls and that will remain, because a token cannot do more than its creator is allowed to do.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.