Authentication
Sign users in with their Connect account and call APIs on their behalf with OAuth 2.0.
Connect APIs accept OAuth 2.0 bearer access tokens. When your app acts for a Connect user, its token only allows what that user's role permits, within the scopes they granted.
Flows
| Your integration | Flow |
|---|---|
| Acts for Connect users (web, desktop or mobile app) | Authorization code with PKCE, then refresh tokens |
| Server-to-server, within your own organisation | Client credentials |
| MCP client (AI assistant) | Authorization code with PKCE, registered automatically through dynamic client registration |
Sending the token
Send the access token in the Authorization header on every request:
curl https://connect.cambrionix.com/api/v1/... \
-H "Authorization: Bearer $ACCESS_TOKEN"
Consent and scopes
When a user authorises your app, Connect shows a consent screen with your app name and the scopes you requested. Ask for the narrowest scopes your integration needs. Once app review opens, apps that pass review will be marked as verified on that screen.
Access tokens are issued for one Connect organisation at a time.