All Composer API customers must migrate to the Composer API on the Conga Platform by February 23rd. Any Composer API solutions that are not migrated by this date will cease functioning February 24th until migration is complete. 
Composer API endpoints found in Getting Started with Composer APIs will no longer be supported starting March 1st. 

Why have we made this decision? 

The Conga Platform is where all future enhancements to the Composer API will take place. Customers will benefit immediately after migration to the Composer API on Platform with improved error messaging and all upcoming enhancements. 

Who will this impact?

All Composer API users that have implemented the endpoints found in Getting Started with Composer APIs will need to migrate to the Composer API Platform by February 23rd. Failure to do so will result in Composer API solutions failing beginning February 24th until the migration is complete.

Migration Steps to take:

  1. Conga provisions existing Composer API customers with a Conga Platform org. This has been completed automatically for existing customers. 
  2. Once provisioned, you will receive an email with the Conga Platform Admin login credentials. This email is sent to the technical contact on file. 
  3. Access the Conga Admin page at https://rls.congacloud.com and select Conga Idp. Input your Conga Platform Admin login credentials.
  4. Click the upper-left icon and select the Admin Console option and choose Organization.
    1. Click the Conga API Connections tab, click Add API To API Connection. 
    2. Select External Identifier from the dropdown list and provide a name for this connection. Click Save & Generate Client Secret. A new 'Client Id' and 'Client Secret' will be generated and displayed. Click Copy and store both of them in a secure location. 
  5. Migrate the Conga Auth Service API:
    1. Replace the url https://services.congamerge.com/api/v1/auth/connect/token with the following url: https://login-rls.congacloud.com/api/v1/auth/connect/token
    2. Update the Client ID and Client Secret with your newly generated ID and Secret.
  6. Migrate the Conga Merge Service API:
    1. Replace the URL https://services.congamerge.com/api/v1/ingress/Merge with the following URL: https://coreapps-rlsprod.congacloud.com/api/ingress/v1/Merge

  7. Migrate the Status Service API:

    1. Replace the URL https://services.congamerge.com/api/v1/status/v1/Status/{CorrelationId} with the following URL : https://coreapps-rlsprod.congacloud.com/api/status/v1/status/{CorrelationId}

  8. Migrate the Download Service API:

    1. Replace the URL https://services.congamerge.com/api/v1/presigned/v1/PreSignedService/{CorrelationId} with the following URL: https://coreapps-rlsprod.congacloud.com/api/presigned/v1/PreSignedService/{CorrelationId}
    2. Replace the URL in the response https://coreapps-rlsprod.congacloud.com/v1/presigned/v1 with the following URL: https://coreapps-rlsprod.congacloud.com/api/presigned/v1/ to obtain the merged file download URL.