Airtable · api · fg-0431

Airtable returns 403 INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND with a valid personal access token

403 INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND

Verified 2026-10-15 · Confirmed by 0 builders · Trust 50/100

Cause

A personal access token needs both the right scope (such as data.records:write) and the base added as a resource, and it can never do more than its creator can in that base. Missing either one looks the same as a wrong base or table ID.

Fix

Edit the token, add the base under Access and the needed scopes, and confirm the creator has editor access. On Enterprise, check whether admins block API access to organization-owned bases.

Apply

https://airtable.com/create/tokens > edit the token > add scopes data.records:read and data.records:write > add the target base as a resource > save

Affects: Airtable Web API, personal access tokens, as of 2026-10

Sources

Have your agent know this before it fails

claude mcp add --transport http footgun https://getfootgun.com/api/mcp