Attach credentials
Each API Request tool should reference one credential from your organization’s vault. Chatevo applies auth at execution time — tokens and keys are encrypted, never shown to visitors, and not included in chat context.
Attach a credential
Section titled “Attach a credential”- Create a credential first (or pick an existing one).
- Open the API Request tool → Authentication / Credential.
- Select the credential that matches your API’s auth scheme.
- Save and test — a 401 usually means wrong credential type or expired token.
Supported types
Section titled “Supported types”| Type | Best for |
|---|---|
| Bearer token | Static or long-lived JWT/API tokens |
| API key | Header or query key |
| OAuth 2.0 | Authorization-code or client-credentials flows |
| HMAC | Signed requests (custom APIs, webhooks-style auth) |
One credential, many tools
Section titled “One credential, many tools”Reuse the same credential across tools that hit the same API base URL. Rotate secrets in Credentials — linked tools pick up the new value without redefining URLs.
What the model sees
Section titled “What the model sees”The tool schema exposes parameter names and descriptions only. Credential values are injected server-side when Chatevo calls your API.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Check |
|---|---|
| 401 Unauthorized | Credential type, header name, token expiry |
| 403 Forbidden | Scopes or API key permissions on your side |
| Wrong tenant | Separate credentials per environment |
See Troubleshooting tool errors and 401 guide.