The Sahut API uses API key authentication. Every request must include your API key in theDocumentation Index
Fetch the complete documentation index at: https://docs.sahut.id/llms.txt
Use this file to discover all available pages before exploring further.
Authorization header. There are no other authentication methods for the REST API.
Generate an API key
- Log in to your Sahut workspace
- Go to Settings → Integrations → API Keys
- Click Buat API Key (Create API Key)
- Enter a label to identify this key (e.g., “CRM Integration” or “Chatbot”)
- Click Buat (Create)
- Copy the key immediately — Sahut only shows the full key once
Pass the API key in requests
Include your API key in theAuthorization header of every request using the Bearer scheme:
Authentication errors
If your API key is missing or invalid, the API returns:- Key not included — You forgot the
Authorizationheader - Wrong format — Use
Bearer YOUR_KEY, not justYOUR_KEY - Key revoked — The key was deleted; generate a new one
- Wrong workspace — The key belongs to a different workspace
Revoking API keys
If an API key is compromised or no longer needed:- Go to Settings → Integrations → API Keys
- Find the key by its label
- Click Cabut (Revoke)
401 Unauthorized response.
Security best practices
- Never expose API keys in client-side code — Your API key in front-end JavaScript is visible to anyone who views your page source
- Use environment variables — Store keys in
.envfiles or your platform’s secret manager - Create separate keys per integration — This way you can revoke one key without breaking others
- Rotate keys periodically — Especially for keys used in production systems