Where to find it
API keys are under Settings → API keys. Every admin can open the tab to see and revoke the existing keys. Creating a key needs an admin with a Pro seat, or any admin of an Enterprise workspace.
Creating a key
- Open Settings → API keys.
- Give the key a name you'll recognise (for example "Zapier" or "nightly export").
- Tick the scopes it needs (at least one), such as
records:readorrecords:write. Grant only what the integration requires. - Click Create key and copy the key straight away. It starts with
tbl_live_and is shown only once. If you lose it, revoke it and create a new one.
What a key can do
A key belongs to the workspace, not to a person. Every key can read the workspace data the API exposes; its scopes decide what it can change. It only works inside your own workspace, and it keeps working until you revoke it, even if the admin who created it leaves. If the subscription is suspended or canceled, every key becomes read-only until billing is sorted out.
Use the REST API to read and sync records, projects, people and templates and, with the right scopes, create, edit, delete and restore records, upload attachments, move records through workflow steps that have owners, manage projects, and change people's names and roles. Some scopes, like members:write, only work on Enterprise workspaces. Templates are read-only through the API.
Treat keys like passwords: never commit them to a code repository, and revoke any key you no longer use.
Reference
The full REST reference, with every endpoint and its request and response format, is under API reference in the Developers menu, and linked from View the API reference in Settings. AI assistants can also connect through MCP.