Get started with the Sybill API

The Sybill API gives you programmatic access to your Sybill workspace over standard REST endpoints. You can export conversations, deals, accounts, messages, and documents, import your own records for Sybill to process, and ask Sybill AI questions about your organization's data.

All endpoints live under a single base URL:

https://api.sybill.ai

Create an API key

API keys are created in the Sybill dashboard under Settings → Integrations → API Keys (app.sybill.ai/settings/integrations/api-keys). Each key belongs to your organization and is granted specific permissions when you create it.

Keys start with the prefix sk_live_ followed by a random token.

⚠️ The full key is shown only once, at creation time. Store it securely — you cannot view it again later.

Authenticate your requests

Pass your key as a Bearer token in the Authorization header of every request:

curl -H "Authorization: Bearer sk_live_YOUR_KEY" \   https://api.sybill.ai/v1/conversations

Permissions and scopes

Each key holds one or more permissions. The dashboard shows a friendly permission name; requests and error messages use the matching API scope value. A single key can hold multiple scopes.

Permission	API scope	What it allows
Export	`read`	Read organization-visible data: all `GET` endpoints for conversations, deals, accounts, messages, rows, documents, sources, and object types
Import	`ingest`	Import and manage your own records: all `POST`, `PATCH`, and `DELETE` endpoints
Ask Sybill	`ask_sybill`	Submit questions to Sybill AI and retrieve answers via the Ask Sybill endpoints

GET /v1/health is the one exception: any valid key can call it, regardless of scopes.

Make your first request

The health endpoint validates your key and returns your organization ID and the scopes the key holds:

curl -H "Authorization: Bearer sk_live_YOUR_KEY" \   https://api.sybill.ai/v1/health

A successful response looks like:

{   "status": "ok",   "org_id": "your-org-id",   "scopes": ["read"] }

Health requests do not count toward your rate limits, so this is a safe way to test connectivity.

If a request is rejected

Two status codes cover authentication problems:

401 Unauthorized - the API key is invalid or has been revoked.
403 Forbidden - the Authorization header is missing, or the key is valid but lacks the scope the endpoint requires. The error names the missing scope:

{   "detail": "API key missing required scope: read" }

Revoke a key

Revoke keys from the same dashboard page where you created them. Revocation takes effect immediately and is permanent — a revoked key cannot be restored, so create a new key if you need access again.

Next steps

Export data from Sybill - read conversations, transcripts, recordings, deals, accounts, and messages.
Import data into Sybill - bring your own conversations, messages, documents, and custom records into Sybill.
API pagination, rate limits, errors, and conventions - cross-cutting behavior every integration should handle.
Use Ask Sybill through the API and MCP - ask Sybill AI questions from your own code or an AI assistant.