Creating personal access tokens

1. With Airtable open, click on your account in the upper right corner of the screen. Here you'll see a dropdown menu appear. Click the Developer hub option. Or if you are currently signed into Airtable, you can click here to access the developer hub.
    

2. This will bring you to the Personal Access Tokens page of the hub. From here you'll click the blue + Create new token option near the top right portion of the screen.

3. This will open configuration options for the PAT that you are creating. 

4. First name the PAT, then choose the scopes you'd like this PAT to have access to. More information on which scopes we currently offer can be found here.
    

5. Finally, choose what level of access this PAT will have. Options include choosing a single base, multiple bases (even 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.
    

Note

This PAT feature grants admins special access to include workspaces and bases added to their organization over time. Importantly, 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 will adopt the user role permissions for those bases and workspaces.

1. From the developer hub scroll to or search for the name of the PAT that you would like to modify. Then, click that token's name.
    

2. Next, modify the name, scopes, or access for the PAT. Note that you can add or remove scopes and access.
    

3. Once you are satisfied with the changes be sure to click Save changes.

1. From the developer hub scroll to or search for the name of the PAT that you would like to modify. Then, click the three-dot spillover to the far right side of that PAT.

2. From here, click the option you need to use.
   

3. 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.

4. Deleting a token will also cause a warning message to appear. Any services currently using this token to access data in Airtable will no longer be able to after you press Delete.

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.