Airtable API
api_key query parameter removal on /v0/*
Stopped workingSubscribe to Airtable APIShare
On February 1, 2024, Airtable removed support for authentication using the api_key query parameter across all /v0/* endpoints. Requests that pass tokens through this URL parameter now fail. The change affects any call relying on the legacy query parameter rather than standard header authentication.
Calls it hits
/v0/*query parameter api_key
What to use instead of these calls
Send a personal access token or an OAuth access token in the Authorization: Bearer header instead of using the api_key URL parameter. Because user API keys no longer work, you must create a personal access token or configure OAuth with the necessary scopes.
User API keys no longer work: someone must create a personal access token or set up OAuth with the right scopes.
In Airtable API's words
Passing personal access tokens and OAuth access tokens via the legacy `api_key` URL parameter is not supported.
Facts
- API
- Airtable API
api.airtable.com - Kind
- Parameter removal
- Announced
- January 18, 2023
- Takes effect
- February 1, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Airtable API's own pages
Questions
When does this change take effect?
Calls to /v0/*, query parameter api_key on Airtable API stopped working on February 1, 2024.
What happens to calls after February 1, 2024?
They have failed since February 1, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Airtable API 1
-
No date
/v0/meta/enterpriseAccounts/{id}/auditLogs*Removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.