Base URL
Request Format
- Use
Content-Type: application/jsonfor request bodies - Include authentication credentials with every request (see Authentication)
- URL path parameters are denoted with
{paramName}in the endpoint documentation
Example Request
Response Format
All successful responses return JSON. The structure depends on the endpoint:Authentication Methods
| Method | Use Case | Details |
|---|---|---|
| Session cookie | Browser-based apps | Set automatically after Auth0 login |
| Bearer token | Server-to-server | Pass in Authorization header |
| Public (no auth) | Widget & SMS webhooks | Rate-limited by IP or assistant |
API Sections
Authentication
Session cookies, API keys, and public endpoints.
Errors & Status Codes
Error format, HTTP codes, and handling patterns.
Rate Limiting
Request limits, widget quotas, and backoff strategies.
Endpoint Reference
Browse individual endpoint documentation generated from the OpenAPI spec.
Key Endpoint Groups
| Group | Base Path | Description |
|---|---|---|
| Assistants | /api/assistants | Create, update, and manage AI assistants |
| Chat | /api/chat | Send messages and stream responses |
| Projects | /api/projects | Manage projects and documents for RAG |
| Contacts | /api/contacts | Create and manage contacts |
| Tickets | /api/tickets | Support ticket lifecycle |
| Widget | /api/widget/{assistantId} | Public widget endpoints |
| SMS | /api/sms | Twilio webhook endpoints |
| Webhooks | /api/webhooks | Manage webhook subscriptions |