Public API

Sennith has a REST API so you can drive your workspace — projects, updates, customers, webhooks and more — from your own scripts, tools, or AI agents. Everything the API can do is also available as a CLI command, because both are built from the same contract.

Base URL

All endpoints live under /api/v1 on your Sennith instance:

https://sennith.com/api/v1

Authentication

Every request carries an API key as a Bearer token:

Authorization: Bearer sennith_...

Keys always start with the sennith_ prefix. You create them in the web app under Settings → API keys (workspace keys) or in your Organization settings (organization keys). The full key is shown once at creation time — copy it then, because Sennith only stores a hashed version and can never show it to you again. If you lose a key, revoke it and create a new one.

The two key levels

Sennith keys come in two levels, and a key only ever works at its own level — there are no all-powerful "god" keys.

A workspace key is tied to exactly one workspace and can never reach organization-level endpoints. An organization key manages the org and never touches a single workspace's day-to-day data. If you send a workspace key to an org endpoint (or the reverse), the request is refused with 403 wrong_key_level.

Scopes

Each key carries a list of scopes — fine-grained permissions of the form resource:action (e.g. projects:read, updates:write, customers:delete). A request only succeeds if the key holds the scope the endpoint requires. A key can never be granted more than its creator personally has permission to do.

Workspace-key scopes (chosen when you create a workspace key):

• projects, updates, customers, customer_contacts, customer_portal_domains — read / write / delete
• triggers — read / write / delete · outgoing_webhooks — read / write / delete
• update_templates — read / write / delete · resource_shares — read / write / delete
• members — read / write / delete · permissions — read / write · routing — read / write
• workspace — read / write · integrations — read · settings — read / write

Organization-key scopes (Team plan and up):

• org — read / write · workspaces — read / write / delete
• org_members — read / write / delete · org_roles — read / write / delete · org_permissions — read / write
• billing — read · settings — read / write

Requests and responses

Send and receive JSON. Request bodies use camelCase field names.

A single resource comes back wrapped in data:

{ "data": { "id": 42, "name": "Website relaunch", "publicId": "a1b2c3", "createdAt": "2026-07-12T10:00:00Z" } }

A list comes back as an array under data, with a next_cursor for pagination — pass it back as ?cursor= to get the next page; null means you've reached the end:

{ "data": [ /* … */ ], "next_cursor": 41 }

Lists accept ?limit= (default 25, max 100) and ?cursor=.

Errors always have the same shape — a stable machine-readable error code plus a human message:

{ "error": "forbidden", "message": "Missing required scope" }

Rate limits

Each key may make up to 120 requests per minute. Beyond that you get 429 rate_limited; wait for the next minute and retry.

Example endpoints

curl https://sennith.com/api/v1/projects \
  -H "Authorization: Bearer sennith_..."

curl -X POST https://sennith.com/api/v1/projects \
  -H "Authorization: Bearer sennith_..." \
  -H "Content-Type: application/json" \
  -d '{ "name": "Website relaunch" }'

curl -X POST https://sennith.com/api/v1/projects/42/updates \
  -H "Authorization: Bearer sennith_..." \
  -H "Content-Type: application/json" \
  -d '{ "title": "Staging is live", "message": "Preview it at the link below.", "isImportant": true }'

curl https://sennith.com/api/v1/whoami \
  -H "Authorization: Bearer sennith_..."

{ "data": { "level": "workspace", "orgId": 7, "workspaceId": 12, "scopes": ["projects:read", "projects:write", "updates:write"] } }

Other resources follow the same pattern: GET /api/v1/<resource> to list, GET /api/v1/<resource>/<id> to fetch one, POST to create, PATCH to update, DELETE to remove — whenever the key holds the matching scope. Available resources include customers, updates, triggers, outgoing_webhooks, update_templates, members, and (with an organization key) workspaces, org_members, org_roles, and billing.

Where to go next