Developer Documentation
SARA API Documentation
Integrate SARA into your existing systems. RESTful APIs, webhook endpoints, and streaming responses — everything you need to build on the SARA platform.
Authentication
All API requests require authentication via a Bearer token in theAuthorizationheader. API keys are generated in your Command Center dashboard under Settings → API Keys.
// Include this header with every request
Authorization: Bearer YOUR_API_KEY
// Example
curl -H "Authorization: Bearer sk_live_abc123..." \
https://cruciblegroupai.com/api/saraSecurity Note: Never expose your API key in client-side code. Use server-side requests or a proxy endpoint. Keys that appear in public repositories will be automatically revoked.
Endpoints
Rate Limits
| Endpoint | Rate Limit | Burst |
|---|---|---|
/api/sara | 60 requests/min | 10 requests/sec |
/api/tts | 30 requests/min | 5 requests/sec |
/api/lead-capture | 120 requests/min | 20 requests/sec |
/api/consult/book | 10 requests/min | 2 requests/sec |
Webhooks | 60 requests/min | 10 requests/sec |
Rate limits are applied per API key. Enterprise plans include higher limits. Contact support for custom rate limit requirements. Exceeded limits return a 429 Too Many Requests response.
Error Handling
All errors follow a consistent JSON format with an HTTP status code, error type, and human-readable message.
{
"error": {
"code": "invalid_request",
"message": "The 'messages' field is required and must be a non-empty array.",
"status": 400
}
}Bad Request
Invalid or missing parameters
Unauthorized
Missing or invalid API key
Forbidden
Insufficient permissions
Not Found
Resource does not exist
Too Many Requests
Rate limit exceeded
Internal Error
Server-side error (retry)
Need help integrating?
Our engineering team can help you integrate SARA into your existing stack. Book a technical consultation or reach out to developer support.