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

TL;DR

I switched my airtable.js code from an API key to a personal access token, since Airtable is deprecating API keys. The library needs no code change: you pass the PAT in the same apiKey option and airtable.js already supports PATs.

Steps

1. 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?
2. 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.

When to use

You are seeing this: Now every request returns 403. Use this skill when you run into "airtable.js returns 403 after switching from API key to personal access token".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.