Skip to main content
Use these endpoints to initiate OAuth/OpenID flows. Login endpoints are browser-oriented and return redirects; callback endpoints receive the provider response.
Integrations must be enabled before you use their OAuth endpoints. See the operator guides for Confluence and SharePoint.

​
Basic request and response

Start a login flow by calling a provider login endpoint and following the redirect.

​
User SSO login redirects

curl -i "https://{BASE_URL}/api/v1/auth/google/login"

HTTP/1.1 302 Found
Location: https://accounts.google.com/o/oauth2/v2/auth?client_id=...&redirect_uri=...

​
Integration OAuth login redirects

curl -i "https://{BASE_URL}/api/v1/app/integration/confluence/login"

HTTP/1.1 302 Found
Location: https://auth.atlassian.com/authorize?client_id=...&redirect_uri=...

​
Login with a specific integration instance

curl -i "https://{BASE_URL}/api/v1/app/integration/confluence/{integrationID}/login"

HTTP/1.1 302 Found
Location: https://auth.atlassian.com/authorize?client_id=...&state=conf_8a7b6c5d4e3f2a1b

​
Refresh an integration token

curl -X POST "https://{BASE_URL}/api/v1/app/integration/confluence/{integrationID}/refresh_token" \
  -H "Authorization: Bearer {API_TOKEN}"

"ok"

​
Callback endpoints

curl -i "https://{BASE_URL}/api/v1/auth/microsoft/callback?code=...&state=..."

HTTP/1.1 302 Found
Location: https://{BASE_URL}/app/login/success

​
Errors and edge cases

  • 302 redirect: expected for login and callback routes.
  • 401/403: token missing for refresh.
  • 404: integration ID not found.