redirect_uri with a single-use authorization code.
This is a browser redirect, not an API call - do not fetch it from your backend.
Endpoint
Authentication
None. The user authenticates with Chamelio on the consent screen.Query Parameters
Request Example
Generate a PKCE verifier and challenge, then send the user to the authorize URL.Response
Success Response
Status Code:302 Found
The user is redirected to Chamelio’s consent screen. Once they approve, their browser is redirected
to your redirect_uri with the authorization code appended:
code immediately at POST /oauth/token.
If the user declines, the redirect carries an error instead:
Error Responses
Errors arrive in one of two ways depending on whether Chamelio can trust yourredirect_uri yet.
400 Bad Request
Returned directly in the browser, without redirecting, when the request cannot be trusted enough to bounce back:Redirect errors
Once the client and redirect URI are validated, remaining problems are returned to yourredirect_uri as query parameters - error, error_description, and your original state:
Notes
The consenting user must belong to the same organization as the application. A user from another
organization attempting to approve gets a
403 on the consent screen. If the user belongs to more
than one organization, the consent screen shows an organization picker. They must select the
organization that owns your application.A pending authorization request expires if the user does not act on it - around ten minutes by
default. After that they must start the flow again.
Use Cases
- User sign-in for your integration - Let each user connect their own Chamelio account
- Least-privilege access - Request only the scopes a feature actually needs
- Multi-user products - Give every user their own token instead of sharing one credential