API keys authenticate requests to the Talvo REST API. They are created and revoked in Settings → Developers.
Creating a key
Give the key a name that says where it will be used, then create it. Keys are prefixed talvo_sk_.
Shown with our demo workspace.
The full key is shown exactly once, at creation. Talvo stores only a hash of it, so we cannot show it to you again or recover it. Copy it into your secret store immediately; if you lose it, revoke it and create another.
Using a key
Send it as a bearer token:
Authorization: Bearer talvo_sk_your_key_here
A key is scoped to the workspace that created it. It cannot read or write another workspace's data.
Revoking
Revoke a key from the same screen. Revocation takes effect immediately — any request using it starts failing straight away. Revoke rather than delete-and-hope if a key may have leaked.
Who can manage keys
Creating and revoking keys is owner and admin only, and both actions are written to the audit log, so there is a record of who issued what.
Good practice
- One key per integration, named for it — so revoking one thing does not break everything.
- Never put a key in front-end code. It is a secret; anything in a browser is not.
- Rotate on a schedule, and whenever someone with access leaves.
