API tokens
Create a token that lets an AI tool or another program reach your organization without signing in.
Only an Owner or Admin can create and manage API tokens.
An API token is a secret key tied to one organization. Anyone who has it can act in that organization with the role the token carries.
When to use a token
- Your MCP client can't sign in with a Sonat account. Claude, ChatGPT and Cursor can, so they don't need one. See Connect Claude, ChatGPT or Cursor.
- You run a script or integration that needs steady access to your organization.
Create a token
- In the left sidebar, select Organization Settings.
- Open the API Tokens tab.
- Select New API token.
- Under Name, enter something that tells you what uses the token, for example Docs sync script.
- Under Role, pick Reader, Writer or Admin.
- Select Create.
- In Save your new API token, select Copy and store the token somewhere safe, such as a password manager.
- Select I've copied it.

Which role to choose
| Role | What the token can do |
|---|---|
| Reader | Read documents and topics, including drafts. Good for search and question answering. |
| Writer | Everything Reader can, plus create, edit, publish and delete content. |
| Admin | Everything Writer can, plus organization-level actions. Use it only when a program really needs it. |
Give each tool its own token with the lowest role it needs. That way you can remove one without breaking the others.
Use a token with an MCP client
The dialog that shows your new token also shows the MCP endpoint and a ready-to-paste Claude Desktop configuration with the token filled in. For other clients:
- Point the client at
https://mcp.sonat.com/mcp. - Send the token in an
Authorization: Bearer <token>header.
Rename, change or delete a token
- To rename a token or change its role, select the edit (pencil) button in its row, make the change and select Save.
- To delete a token, select the delete (trash) button in its row and confirm with Delete. Anything that uses the token stops working right away.
Keep tokens safe
- Don't paste a token into a chat, a shared document or source code that others can read.
- If a token may have leaked, delete it and create a new one.
- Review the list now and then and delete tokens nothing uses anymore.