API tokens
Everything you can do in the dashboard — launch an instance, list them, read connection details, start and stop — is backed by the same API. Scoped tokens let you call it from scripts and CI.
Create a token
From your workspace, open API tokens and create one. Give it a name and copy the value immediately — it's shown once. Revoke a token any time from the same page; it stops working immediately.
A token belongs to the workspace and inherits the resource permissions of the role that minted it — a viewer's token can read, not create. It never carries workspace-management rights: a token cannot invite members, change roles, or delete the workspace that issued it.
Use it
Attach it as a bearer token on your requests:
curl "https://api.sahabti.com/v1/servers?orgId=$WORKSPACE_ID" \
-H "Authorization: Bearer $SAHABTI_TOKEN"
Creating an instance is the same shape:
curl -X POST https://api.sahabti.com/v1/servers \
-H "Authorization: Bearer $SAHABTI_TOKEN" \
-H "Content-Type: application/json" \
-d '{"engine":"postgres","name":"orders","plan":"small","orgId":"'"$WORKSPACE_ID"'"}'
The instance routes cover create, list, get, start, stop, restart, delete, connection details, the provisioning log, and metrics. The API publishes its own reference at /docs.
Next steps
- New here? Start with getting started
- Instances — what each lifecycle action does