Skip to main content
Complete the following prerequisites and configuration to start using the Smarty Connector.

​
Prerequisites

Before you begin, make sure that the following requirements are met:
  • You have completed the steps in the Getting started.
  • You have an active contract with Smarty and your own accounts and credentials set for Smarty services.

​
Configuration

To configure your connector, follow these steps:
  1. Set your APIM subscription key in the header as follows:
    • Key: api-key
    • Value: <your subscription key>
  2. Request the Grand Central team to set up a connection with Smarty, and provide the following details for OAuth token generation:
    • smarty-us-license
    • smarty-us-metadata-license
    • smarty-int-license
    • smarty-auth-id
    • smarty-auth-token
  3. Configure the Smarty baseURL in the gc-applications-live repository in the connector’s values.yaml file: 
    smarty.int.base.url = //SMARTY environment base URL for International Address AutoComplete
smarty.us.base.url = //SMARTY environment base URL for US Address AutoComplete
smarty.us.metadata.url = //SMARTY environment base URL for US Address Validation
  4. Verify the connector’s values.yaml file location in the repository: 
    ├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            └── gc-smarty
                └── location-data-management-v1.values.yaml

​
Test your integration

To access the Location Data Management Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central 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 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. If the service is operational, contact the Grand Central team.
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. If the service is operational, contact the Grand Central team to review timeout configurations.
Cause: The credentials provided during setup are incorrect.Solution: Verify your credentials with Smarty and contact the Grand Central 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.