Skip to main content
Every request carries a Bearer token:
Three kinds of token reach the same API. The prefix tells you which you hold.

​
Create a token

In the dashboard, go to Developers → API tokens and create one. You choose a role for the token and, optionally, an expiry.
The full token is shown once at creation. Store it somewhere safe. Sentivel keeps only a hash and can never show it again. If you lose it, revoke it and create a new one.
Create a personal token under Account → API tokens. It acts as you, so it carries your own role in every workspace you belong to. A connected app receives its token through OAuth, and you choose which workspaces it may reach when you approve the connection. Revoke either under Account.

​
Name a workspace

An org token is bound to one workspace, so there is nothing to choose. A personal or connected-app token can reach several. Name one per request:
Omit the header and the request goes to your primary workspace. When the token can reach more than one and the choice is ambiguous, you get a 400 invalid_request listing the candidates in details.workspaces. Retry with the header set.

​
What each role can do

An org token is never an owner, because owner is not one of the roles you can give it. A personal or connected-app token acts as you, so GET /me reports owner when that is your role. Billing, member management, and workspace deletion are not API operations either way.

​
Errors