OAuth 2.0

OAuth 2.0 credentials manage access tokens with automatic refresh — for APIs that issue short-lived tokens via authorization code or client credentials grants.

Supported flows

Flow	Use when
Client credentials	Machine-to-machine, no user login
Authorization code	User-delegated access to a provider (CRM, calendar, etc.)

Exact provider fields depend on your OAuth server — Chatevo stores client ID, client secret, token URL, and scopes encrypted.

Create (client credentials)

1. Credentials → Create → OAuth 2.0.
2. Name — e.g. CRM API OAuth.
3. Grant type — Client credentials.
4. Token URL — provider token endpoint.
5. Client ID and Client secret.
6. Scopes — space-separated if required.
7. Save → Chatevo fetches and refreshes tokens automatically.

Create (authorization code)

1. Register redirect URI with your OAuth provider (Chatevo shows the callback URL).
2. Enter authorization URL, token URL, client ID, secret, and scopes.
3. Click Authorize in the dashboard to complete consent.
4. Attach credential to tools.

Runtime behavior

Chatevo requests or refreshes tokens before tool calls. The model never sees access or refresh tokens.

When to use OAuth vs Bearer

OAuth 2.0	Bearer token
Expiring access tokens	Long-lived static token
Provider requires refresh	Simple PAT from vendor dashboard

Troubleshooting

Issue	Check
401 after weeks	Re-authorize; confirm refresh token valid
invalid_client	Client ID/secret mismatch
insufficient_scope	Add scopes on credential

See Troubleshooting tools.

Related

• Credentials overview
• Bearer token
• Attach credentials