Authentication

Conga’s REST API authentication requires a bearer token. An account administrator can generate tokens for inclusion in authentication requests. Requests can then be included in scripts, configuration files, applications, processes, and so on.

Prerequisite

You can either use any of the following flows, as per your business requirements, to generate the authentication token:

1. A client ID and client secret of the integration user are generated. For more information on how to create an Integration User and get the client ID and secret, see Adding Users.
2. A client ID and client secret are generated for the API connection. For more information on how to generate ID–secret pairs, see Conga API-to-API Connection.

Generate Authentication Token

The Auth Access Token API call returns a Conga access token to authorize API calls.

• HTTP Method: POST

• Region Specific Endpoint:

  Production Environment	Preview Environment
  NA: https://login-rls.congacloud.com/api/v1/auth/connect/token	NA: https://login-rlspreview.congacloud.com/api/v1/auth/connect/token
  EU: https://login.congacloud.eu/api/v1/auth/connect/token	EU: https://login-preview.congacloud.eu/api/v1/auth/connect/token
  AU: https://login.congacloud.au/api/v1/auth/connect/token	AU: <https://login-preview.congacloud.au/api/v1/auth/connect/token

  
  

• Post Body:

  • grant_type: ‘client_credentials’
  • client_id: {review the prerequisite and add generated client ID}
  • client_secret: {review the prerequisite and add generated client secret}

    📘

    You must include the platform user ID in the authentication token request when you use the Conga API-to-API flow. Login to the Conga Advantage Platform and get the user ID.