Skip to main content
Follow the steps in Get started with connectors before proceeding. Salesforce access: An active account in the Salesforce production or sandbox environment. Network connectivity: Verify that your network routes traffic between the Salesforce environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the Salesforce login URL and the connected-app credentials for the authentication type you use. Username and password authentication needs a client ID, client secret, username, and password. Refresh-token authentication also needs a refresh token.

​
Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and Salesforce as described in Network connectivity.
  2. Send environment details to Backbase. Send the Salesforce login URL and the connected-app credentials to your Backbase support team.
For property names and defaults, see Reference.

​
Testing your integration

To use the Unified API, include your Banking OS subscription key in the request header. If you don’t have a key, contact your Backbase support team to request one. Test the API using the GC Activity Postman collection (includes get-by-party and get-by-employee samples).

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS gateway cannot establish a handshake with the Salesforce endpoint. This typically indicates an upstream service outage at Salesforce or a network routing failure.Solution: Verify the operational status of the Salesforce environment. Check the Salesforce status page or contact Salesforce support.
Cause: The request to Salesforce exceeded the configured timeout period. This may indicate performance issues at Salesforce or network latency problems.Solution: Verify the operational status of the Salesforce environment and check for any performance degradation.
Cause: The OAuth credentials provided during setup are incorrect, expired, or you lack the required permissions in Salesforce.Solution: Re-verify your credentials with your Salesforce administrator and ensure you have the required permissions. Contact your Backbase support team to update the connection credentials if needed. To store connector credentials, see Credentials.
Cause: The party ID or activity ID (Salesforce Contact / Task / Event ID) you include in the request is invalid or does not exist in Salesforce.Solution: Verify that the ID is a valid Salesforce identifier (15 or 18 characters). Check that the Contact, Task, or Event exists in your Salesforce org and the ID format is correct.
Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Banking OS and Salesforce infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact your Backbase support team to request a higher rate limit.