Skip to main content
Follow the steps in Get started with connectors before proceeding. Smarty access: An active contract with Smarty, with accounts and credentials for Smarty services.

​
Prepare the connector

Backbase deploys this connector. To provide the environment details, follow these steps:
  1. Send environment details to Backbase. Send smarty-us-license, smarty-us-metadata-license, smarty-int-license, smarty-auth-id, smarty-auth-token, and the Smarty base URLs to your Backbase support team.
For property names and defaults, see Reference.

​
Test your integration

To access the Location Data Management 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 have one provisioned. Test the API using the Postman collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS gateway cannot establish a handshake with the Smarty endpoint. This typically indicates an upstream service outage at Smarty or a network routing failure.Solution: Verify the operational status of the Smarty environment with Smarty.
Cause: The request to Smarty exceeded the configured timeout threshold. This can occur during high load or network latency issues.Solution: Verify the operational status of the Smarty environment with Smarty.
Cause: The credentials provided during setup are incorrect.Solution: Verify your credentials with Smarty and contact your Backbase support 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 Banking OS and partner infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If you require higher throughput, contact your Backbase support team to request an adjustment to your APIM rate limit policy.