Developers
API authentication and safe integration
Authenticate tenant-scoped Chattill API requests, store credentials safely and handle quotas and errors.
For Developers and technical administrators8 min readUpdated
Choose the correct credential
| Credential | Use |
|---|---|
| Organization API key | Preferred for tenant-scoped /api/v1 integrations. |
| Personal API token | User-scoped access where explicitly supported; it follows that user’s organization access. |
| Inbound sender token | Dedicated credential for POST /api/send from an external system. |
| Browser session | Interactive Chattill UI only; do not copy its cookie into an integration. |
Send an organization API key
http
Authorization: Bearer YOUR_API_KEYCreate keys from the authenticated API Keys page when your plan includes the public API. A key is shown only when created. Store it in a server-side secret manager, never in browser JavaScript, screenshots or source control.
Handle responses defensively
| Status | Action |
|---|---|
| 400 | Fix the request fields or query format. |
| 401 | Provide a current supported credential. |
| 403 | Check tenant access, plan or organization status. |
| 404 | The tenant-owned resource was not found. |
| 429 | Honor Retry-After and retry with backoff. |
| 5xx | Retry only safe idempotent reads, use backoff, and preserve diagnostics without secrets. |
Machine-readable specification
The supported public endpoints are described in the OpenAPI 3.1 document at /docs/openapi.json. Treat undocumented internal browser endpoints as private and subject to change.
Related guides
Ready to use this in your workspace?
Sign in to continue setup, or review the tenant go-live checklist before sending live traffic.