airtable.js returns 403 after switching from API key to personal access token
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…
Problem outcome: unknown