Conga · OAuth Scopes

Conga OAuth Scopes

OAuth 2.0 searched

Conga publishes 11 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Conga API on a user’s behalf.

Tokens are issued from https://login.conga.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyEnterprise SoftwareContract Lifecycle ManagementCPQRevenue Lifecycle ManagementDocument AutomationE-SignatureContract IntelligenceCRM

Scopes: 11 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://login.conga.com/authorize

Token URL
https://login.conga.com/oauth/token

Flows
authorizationCodeclientCredentials

Scopes (11)

Scope	Description	Flows
openid	OpenID Connect authentication; issue an ID token.
profile	Access to the user's default profile claims.
email	Access to the user's email and email_verified claims.
offline_access	Issue a refresh token for long-lived access.
name	User's full name claim.
given_name	User's given (first) name claim.
family_name	User's family (last) name claim.
nickname	User's nickname claim.
picture	User's profile picture claim.
phone	User's phone number claim.
address	User's address claim.

📄 Provider scope reference: https://developer.conga.com/platform/reference/authentication

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: https://login.conga.com/.well-known/openid-configuration
docs: https://developer.conga.com/platform/reference/authentication
notes: >-
  Conga's REST API authorizes machine-to-machine calls with the OAuth 2.0
  client_credentials grant; access is governed by the Integration User's platform
  permissions rather than by fine-grained API scopes documented per operation.
  The scopes below are the OIDC/identity scopes advertised by Conga's login
  service (login.conga.com) discovery document. No per-resource API scope
  reference is published in the developer docs.
schemes:
- name: DeveloperPortalOIDC
  source: https://login.conga.com/.well-known/openid-configuration
  issuer: https://login.conga.com/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.conga.com/authorize
    tokenUrl: https://login.conga.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://login.conga.com/oauth/token
scopes:
- scope: openid
  description: OpenID Connect authentication; issue an ID token.
- scope: profile
  description: Access to the user's default profile claims.
- scope: email
  description: Access to the user's email and email_verified claims.
- scope: offline_access
  description: Issue a refresh token for long-lived access.
- scope: name
  description: User's full name claim.
- scope: given_name
  description: User's given (first) name claim.
- scope: family_name
  description: User's family (last) name claim.
- scope: nickname
  description: User's nickname claim.
- scope: picture
  description: User's profile picture claim.
- scope: phone
  description: User's phone number claim.
- scope: address
  description: User's address claim.