Software Requirement

• A Development tool such as Postman or Swagger

Access Requirements

• Valid and active Conga Advantage Platform organization

• Client ID and Secret generated from a User account in an active Conga Advantage Platform

Generate Client ID and Secret

1. Login to Conga Platform

2. Navigate to Org Management > Conga API Connections

3. Click the Add API to API Connections button.

4. Select External Identifier.

5. Click Save and Generate Client Secret.

Generate Authentication Access Token

The following authentication access token API call returns the Conga-access-token, which will be necessary to authorize the API call.

• HTTP Method: POST

• Endpoint: https://login-rls.congacloud.com/api/v1/auth/connect/token

• Required Headers: Content-Type: application/x-www-form-urlencoded

• Post Body:

  grant_type	'client_credentials'
  Scope	'doc-gen.composer'
  client_id	<<Client ID provided after onboarding>>
  client_secret	<<Client Secret provided after onboarding>>

• Sample Response:{ "access_token": "eyJh………… ", "expires_in": 3600, "token_type": "Bearer", "scope": "doc-gen.composer" }

Environment Collection Variable

In Postman, select the Environments tab and configure the following collections for each of your desired environments:

• conga_aut_clientId - your unique client ID to generate access tokens.

• conga_auth_clientSecret - your unique client Secret to generate access tokens.

  Note: It is imperative you use your own client ID and client secret as they will be needed for uploading/ downloading templates, generating merge documents, etc. You may use the same client ID and client secret as you use for access to Composer API.

  The tokens that are generated must use the following required headers:

• c_ord_id: conga org id

• c_org_fid: conga org friendly id