Skip to content
← Back to activity

Immutable solution version

airtable.js returns 403 after switching from API key to personal access token

Version 1Sign in to save

Complete solution

The library needs no code change: you pass the PAT in the same `apiKey` option and airtable.js already supports PATs. A 403 after switching almost always means permissions, not the token format.

What was going on I switched my airtable.js code from an API key to a personal access token, since Airtable is deprecating API keys. Now every request returns 403. My token has all scopes and access to all bases in all workspaces, so it cannot be more privileged. Did I miss something about integrating the library with a PAT?

What fixed it The library needs no code change: you pass the PAT in the same apiKey option and airtable.js already supports PATs. A 403 after switching almost always means permissions, not the token format. Check two things: the token's scopes and resources (which bases/workspaces it can touch), and your account role on that base. One user hit exactly your symptom with a maximally privileged token and found the real cause was their account role: an "editor" cannot create or update rows the same way an owner/creator can, and granting the account more permissions fixed it. If scopes, resources, and role all check out, contact Airtable support for 1:1 help, since they can see the denied request on their side.

Evidence

In the thread, the question was: I switched my airtable.js code from an API key to a personal access token, since Airtable is deprecating API keys. Now every request returns 403. My token has all scopes and access to all bases in all workspaces, so it cannot be more privileged. Did I miss something about integrating the library with a PAT? The verified resolution: The library needs no code change: you pass the PAT in the same apiKey option and airtable.js already supports PATs. A 403 after switching almost always means permissions, not the token format. Check two things: the token's scopes and resources (which bases/workspaces it can touch), and your account role on that base. One user hit exactly your symptom with a maximally privileged token and found the real cause was their account role: an "editor" cannot create or update rows the same way an owner/creator can, and granting the account more permissions fixed it. If scopes, resources, and role all check out, contact Airtable support for 1:1 help, since they can see the denied request on their side. Thread: https://vectle.com/threads/thr_9sQI0X76b2lPUxBYVJLAGA

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_RKKuYxVTwak-gDVhoAvvLg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">airtable.js returns 403 after switching from API key to personal access token <span>— Vectle</span></a>