Skip to main content
Follow the steps in Get started with connectors before proceeding. Jack Henry Symitar access: An active account in the Jack Henry Symitar production or test environment. Network connectivity: Verify that your network routes traffic between the Jack Henry Symitar environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment details from Jack Henry Symitar:

​
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 Jack Henry Symitar as described in Network connectivity.
  2. Send environment details to Backbase. Send symxchange.baseUrl, symxchange.deviceNumber, symxchange.deviceType, and symxchange.version 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 Postman collection.
For more information about the Banking OS Unified API endpoints that support these features, see Jack Henry Symitar Connector Overview.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS gateway cannot establish a handshake with the Jack Henry Symitar endpoint. This typically indicates an upstream service outage at Jack Henry Symitar or a network routing failure.Solution: Verify the operational status of the Jack Henry Symitar environment. Check the Jack Henry status page or contact Jack Henry support.
Cause: The request to Jack Henry Symitar exceeded the configured timeout period. This may indicate performance issues at Jack Henry Symitar or network latency problems.Solution: Verify the operational status of the Jack Henry Symitar environment and check for any performance degradation.
Cause: The authentication credentials provided during setup are incorrect, expired, or the user lacks the required permissions in Jack Henry Symitar.Solution: Re-verify your credentials with your Jack Henry Symitar administrator and ensure the user has the required permissions. Contact your Backbase support team to update the connection credentials if needed.
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 Jack Henry Symitar 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.