API keys
Create and revoke bearer tokens for scripts and automations.
An API key lets a script or an automation call Tattva's HTTP API as you. Each key belongs to the person who created it and acts with that person's permissions.
Manas doesn't use API keys. It connects to Tattva with its own gateway secret and acts as the person or Slack channel asking; see Use Tattva from Manas.
Where to find it
Open Settings › API keys, or go to /settings/api-keys. The page reads: "Bearer tokens for scripts and automations that call Tattva's HTTP API, such as Activepieces flows. The token is shown once on creation; we only store its hash."
You see only your own keys, under Your keys (N active).
Creating a key
- Click New API key.
- Enter a Name that says what uses it, for example "Nightly sync".
- Optionally set Expires in (days, optional), from 1 to 3650. Leave it blank for a key that never expires.
- Click Create key.
- In Key created, click Copy and store the token in your secret manager. "This is the only time the full token is shown." After you click Done, only the prefix stays visible.
Using a key
Send it in the Authorization header:
GET /api/projects HTTP/1.1
Host: tattva.example.com
Authorization: Bearer <your token>What a key can do
A key has exactly the permissions of the person who created it. If your role changes, your keys change with it. Keys have no narrower scopes, so treat every key as your own login.
Keys are created and revoked in the browser only. A key can't create another key.
The key list
Each row shows the name, the token prefix, Last used (or Never used), Created, and Expires or Expired. Revoked and expired keys carry a revoked or expired badge.
Revoking a key
Click the revoke icon on the key's row and confirm Revoke this API key?. Anything still using it starts getting 401 errors. A revoked key can't be restored; create a new one.
Rotating a key
There is no automatic rotation. To rotate:
- Create a new key.
- Switch your script or service to it.
- Wait until the old key's Last used stops moving.
- Revoke the old key.
Good practice
- One key per script or service, so revoking one doesn't break the others.
- Set an expiry for short-lived jobs.
- Never commit a key to git.
- Revoke a person's keys when they leave.
Related
Weekly report
What real users' questions did to Tattva's reading over the last week, per project, and the capability gaps for the engineering team. Platform admins only.
Notifications
Where Tattva tells you something changed — the in-app bell, each tracker's Delivery tab, and the subscription settings.