The Sahut REST API lets you integrate Sahut programmatically into your systems. Use the API to sync contacts from your CRM, send proactive messages, retrieve conversation history, or build a chatbot that responds automatically to customer messages. All API requests are made over HTTPS. The API returns JSON for all responses.Documentation Index
Fetch the complete documentation index at: https://docs.sahut.id/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
Request format
Send requests as JSON with theContent-Type: application/json header. For GET requests, pass parameters as query string parameters.
Response format
All responses return a JSON object. Successful responses include adata field containing the result. Error responses include an error object.
Success response:
Error codes
| HTTP Status | Error code | Meaning |
|---|---|---|
| 400 | bad_request | Request is missing required fields or has invalid values |
| 401 | unauthorized | Missing or invalid API key |
| 403 | forbidden | Your API key doesn’t have permission for this action |
| 404 | not_found | The requested resource doesn’t exist |
| 422 | validation_error | Request data failed validation |
| 429 | rate_limited | Too many requests — slow down |
| 500 | server_error | Sahut server error — try again later |
Rate limits
The API enforces rate limits per API key:| Plan | Requests per minute |
|---|---|
| Starter | 60 |
| Pro | 300 |
| Business | 1,000 |
429 Too Many Requests with a Retry-After header indicating how many seconds to wait.
Pagination
List endpoints return paginated results. Use thepage and per_page query parameters to navigate:
Timestamps
All timestamps in the API are in ISO 8601 format (UTC):2024-03-15T08:30:00Z.