Torki API
API Keys, Organizations, Workspaces and Members
Overview
Everything on Torki Platform belongs to an organization: the credit, the usage tier and its limits, the keys and the members. Workspaces divide an organization by project or environment, and API keys belong to a workspace.
Organizations
Your first visit to Torki Platform creates a personal organization. If you belong to more than one, switch between them from the account menu at the bottom of the sidebar (under Organizations) or in Settings → General. An admin can rename the organization in Settings → Organization, which also shows its Organization ID and Usage tier.
Members and roles
Each member has one role. Each role includes everything below it:
| Role | Can |
|---|---|
| User | Use the Playground |
| Developer | + create and manage API keys, see analytics and logs |
| Billing | + buy credit, see invoices, set the spend limit |
| Admin | + members, workspaces, service accounts and organization settings |
| Owner | Everything. There is exactly one per organization. |
Invite your team
Open Members and click Invite members. Enter up to 50 email addresses at once, separated by commas, spaces or new lines, and pick one role for all of them. Invitations are emailed, expire after 21 days and work only for the address they were sent to. Unaccepted ones are listed under Pending invitations, where you can Revoke them.
Teammates share the organization's credit, keys and analytics. A member can leave with Leave organization; an admin can remove someone with Remove from organization.
Workspaces
A workspace groups keys by project or environment, such as Production, Staging or Evals. Usage and cost are reported per workspace, and a workspace can have its own monthly spend limit and lower rate limits — never higher than the organization's. Credit is shared by all workspaces.
- Create one on Workspaces with Create workspace. An organization can have up to 100.
- Each workspace's menu has Rename, Set limits and Archive. Archiving a workspace disables its keys for good.
- Every organization has a Default workspace, which can't be renamed, archived or given its own limits.
API keys
Create a key
Open API keys and click Create key (Developer role or higher).
- Name — something you'll recognise later: the app or the environment.
- Workspace — where its usage, cost and limits are counted.
- Under Advanced, Expires — 3 hours, 1 day, 7 days, 30 days (the default), a custom date or never. After it expires the key returns
401. - Under Advanced, Linked account — Me, or A service account.
Copy the key from the Save your key window with Copy key. It is shown once: Torki keeps only a hash, so a lost key can't be shown again. Create a new one instead.
Manage keys
Each key's menu has Disable (or Enable) and Delete. Disabled, expired and deleted keys return 401. An organization can hold up to 100 keys.
Service accounts
A key linked to a member stops working when that member leaves the organization. For production systems and CI, link keys to a service account instead: its keys keep working when people leave, and archiving the service account disables all of them in one step. Admins create service accounts in Settings → Service accounts with Create service account, or while creating a key.
Keep keys out of client-side code, mobile apps and public repositories. Prefer an expiry and rotate keys. If a key may have leaked, delete it at once on API keys.
FAQ
I lost my key. Can I see it again?
No. Torki keeps only a hash of each key. Create a new key and delete the old one.
My key stopped working after a colleague left.
Keys linked to a member stop working when that member leaves, and they can't be re-enabled. Create a new key, linked to a service account if it is for a production system.
Can a workspace have higher limits than the organization?
No. A workspace can only be stricter than the organization.