Where to find it
API access lives under Settings → API keys. It's available to admins on a Pro seat, and on Enterprise workspaces.
Creating a key
- Open Settings → API keys and choose Create key.
- Give it a name you'll recognise (e.g. "Zapier" or "nightly export").
- Pick the scopes it needs — a key does nothing until you grant at least one (e.g. records read, records write, projects read). Grant only what the integration requires.
- Copy the key once — it starts with
tbl_live_and is shown only at creation. Store it safely; if it's lost, delete it and make a new one.
What a key can do
A key is an organisation-level service credential, not a personal login. It's bounded by the scopes you grant it and by your workspace's tenant isolation, so it can only touch the data those scopes allow, inside your own workspace. (Some scopes, like members:write, are Enterprise-only.) Use the REST API to list and create records, read templates, and pull data into your own tools.
Reference
The full REST reference — every endpoint, with request and response shapes — is published at the API docs link in the Developers menu. AI assistants can also connect via MCP.
Treat keys like passwords: never commit them to a repo, rotate them periodically, and delete any key that's no longer used.