Creating personal access tokens

Prev Next

Plan availability

All plan types. Certain features are only available to Enterprise Scale or Business plan customers.

Permissions

The scopes and access that you can set up with personal access tokens will reflect the permissions that you have in the various workspaces and bases connected to your Airtable account.

Platform(s)

Web/Browser, Mac app, and Windows app

Related reading

What are Personal Access Tokens?

Personal Access Tokens (PATs) allow users to create multiple access tokens that allow for a wide range of access to the information held in Airtable bases. For example, on the narrow end, you can create a PAT that only has a single scope to a single base in Airtable. On the deep end, however, you could have a "main/overarching" token that has access to all workspaces and bases with all available scopes included. Further, admins can adopt user role access on workspaces and bases in their enterprise for which they are not direct collaborators.

Creating personal access tokens

Note

PATs allow admins access to workspaces and bases added to their organization. The admin who owns the PAT does not need to be a direct collaborator on every workspace and base within the organization. Instead, the PAT adopts the user role permissions for those bases and workspaces.

To create personal access tokens:

  1. Open the developer hub.

  2. Click Create token.

  3. Name your token.

  4. Click + Add a scope.

    1. Check out developer documentation to learn more about scopes.

  5. Click + Add all resources/+ Add a base to select your token’s access level.

    1. Options include choosing a single base, multiple bases—including bases from different workspaces—all of the current and future bases in a workspace you own, or even all of the bases from any workspace that you own including bases/workspace added in the future.

To update personal access tokens:

  1. Open the developer hub.

  2. Scroll or search for the name of the PAT that you wan to update.

  3. Click the token's name.

  4. Update the name, scopes, or access for the PAT.

  5. Click Save changes.

To regenerate or delete personal access tokens:

  1. Open the developer hub.

  2. Scroll or search for the name of the PAT that you wan to regenerate or delete.

  3. Click the icon to the far side of the PAT.

  4. Click Edit token, Regenerate token, or Delete token.  

    1. Regenerating a token will cause a warning message to appear. Remember that any services currently using this token will need to be updated with the new token that is generated.

Finding personal access tokens

To find your personal access tokens:

  1. Open the developer hub.

  2. Click Personal access tokens under the “Developers” section.

FAQs

What can my personal access tokens access?

Unlike legacy API keys, which have the same access as your Airtable account, you can limit and configure the access of your personal access tokens. You can do this by selecting the scopes (what endpoints the token can use) and access/resources (which bases and workspaces the token can access) when creating or updating a token. 

Regardless of the scopes and access a user selects for their token, the token will only be able to perform actions that the user creating it is allowed to do. For example, to create a new field in a base via the API, the user must be a Creator collaborator in the base and the token must have the schema.bases:write scope and the base added as a resource. 

For more information about how scopes and access work, see the Authentication developer reference. For more information about configuring your token's access, refer to the personal access tokens guide.

When were API keys deprecated?

On Jan 18, 2023, we began the deprecation period of user API keys, completing the deprecation period on Feb 1, 2024, meaning:

  • API Keys can no longer access the Airtable API.

  • Webhooks created with user API keys will not expire, but can no longer be created.

  • All users should migrate to Personal Access Tokens for individual use and OAuth for third-party integrations.