Skip to main content
Before you configure the connector, ensure you have the following credentials and connectivity in place:
  • You have completed the steps in the Getting started.
  • You have an active contract with ComplyAdvantage and your own accounts and credentials for their test and production services.

​
Configuration guide

Follow these steps to initialize and authorize your ComplyAdvantage Connector.

​
Step 1: Establish connectivity

  1. Set your APIM subscription key in the header as follows:
    • Key: api-key
    • Value: <your subscription key>
  2. Contact the Grand Central team to set up a connection with ComplyAdvantage. Provide the following details for OAuth token generation:
    • comply-advantage-username
    • comply-advantage-password
    • comply-advantage-realm

​
Step 2: Configure environment variables

  1. Configure the base URL in the gc-applications-live repository in the connector’s values.yaml file:
Sample application.properties file: 
complyAdvantage.baseUrl = //COMPLY environment base URL
The following example shows the location of the connector’s values.yaml file: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-complyAdvantage
            └── party-lifecycle-v1.values.yaml

​
Test your integration

To access the Party Lifecycle Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central Support Team to have one provisioned.
KeyValue
api-key<your_subscription_key>
Test the API using the Postman collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central gateway cannot establish a handshake with the ComplyAdvantage endpoint. This typically indicates an upstream service outage at ComplyAdvantage or a network routing failure.Solution: Verify the operational status of the ComplyAdvantage environment with ComplyAdvantage. If the service is operational, contact the GC Support team.
Cause: The request to ComplyAdvantage exceeded the configured timeout threshold. This can occur during periods of high load or network latency.Solution: Verify the operational status of the ComplyAdvantage environment with ComplyAdvantage. If the service is operational, contact the GC Support team to review timeout configurations.
Cause: The credentials provided during setup are incorrect.Solution: Verify your credentials with ComplyAdvantage and contact the GC team to update the connection.
Cause: The number of incoming requests exceeded the defined threshold for your subscription tier. This response protects the stability of the Grand Central and partner infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If you require higher throughput, contact the Grand Central team to request an adjustment to your APIM rate limit policy.

​
Need more help?

Contact support

Reach out to the Grand Central team for assistance with environment setup or rate limit increases.