Authenticate every WorksBuddy API request with the credential the agent expects. Keep keys server side and never expose them in client code.
Credentials by agent
| Agent | Send | Where to get it |
|---|---|---|
| Lio | X-API-Key: CRM_… (a bare key, not a bearer token) | Lio API |
| Taro | Authorization: Bearer wb_live_… | Taro settings, Developer tab (Taro API) |
| Evox | Authorization: Bearer evox_… (Delivery Suite: dlv_…) | Evox API |
| Sigi | Authorization: Bearer wb_live_… (org admin key) | Sigi API |
| Inzo | Authorization: Bearer wb_live_… (sandbox: wb_test_…) | Inzo API |
| Revo | Authorization: Bearer <token> (user JWT, workflow token, or app JWT for external apps) | Revo API |
| Ranko | Authorization: Bearer rfk_… for the public delivery API; WorksBuddy SSO JWT for the app API | Ranko API |
| Ciao | Authorization: Bearer <API_KEY> (X-API-Key is also accepted) | Ciao API |
Example
curl https://api-taro.worksbuddy.ai/api/v1/tasks \
-H "Authorization: Bearer wb_live_YOUR_API_KEY"curl -X POST https://api-lio.worksbuddy.ai/api/v1/lead \
-H "X-API-Key: CRM_YOUR_API_KEY_HERE" \
-H "Content-Type: application/json"Token lifetimes, refresh, and key rotation differ by agent. See the agent's API reference for details.