Get started

Complete the following prerequisites and configuration to start using the SaltEdge Connector.

​

Prerequisites

Before you begin, make sure you meet the following requirements:

• You have completed the steps in Get started with connectors.
• You have an active SaltEdge Data Enrichment contract and the credentials required for API and webhook authentication.
• You have network connectivity between Grand Central and SaltEdge. For supported options, see Network connectivity.

​

Configuration

To configure the SaltEdge Connector, follow these steps:

1. Set your API Management (APIM) subscription key in the header as follows:
   • Key: api-key
   • Value: YOUR_SUBSCRIPTION_KEY
2. Obtain the application credentials for your SaltEdge environment. SaltEdge issues an App-Id and an App-Secret. Grand Central sends both values to SaltEdge as request headers. Store them in a SOPS secret:
   • saltedge-position-keeping-app-id
   • saltedge-position-keeping-secret
3. Configure the SaltEdge base URL and customer ID in the gc-applications-live repository in the connector’s values.yaml file:
   # SaltEdge environment base URL
   saltedge.baseUrl=SALTEDGE_BASE_URL
   # SaltEdge customer ID
   saltedge.customer-id=SALTEDGE_CUSTOMER_ID
   
4. Verify the values.yaml file locations in the repository. Both files are in the gc-saltedge folder. Replace RUNTIME with your runtime name, such as dev or test:
   ├── iPaaS
   └── azure/runtimes
       └── RUNTIME
           └── values
               └── gc-saltedge
                   ├── position-keeping-v0.values.yaml
                   └── position-keeping-inbound-v0.values.yaml
   
5. Expose the SaltEdge categorization webhook at POST {baseInboundURL}/webhooks/transaction-categorizations. Register this URL with SaltEdge.
6. Add the following signature-verification properties to position-keeping-inbound-v0.values.yaml:
   # Flag to enable signature verification
   saltedge.callback.signature.enabled=SIGNATURE_VERIFICATION_FLAG
   # Callback URL to receive the payload
   saltedge.callback.url=CALLBACK_URL
   # Signature public key from the SaltEdge documentation
   saltedge.callback.signature.public-key.v6_0=PUBLIC_KEY
   
7. Configure the following Sync Hub Azure Service Bus (ASB) producer properties in position-keeping-inbound-v0.values.yaml so the transactionsEnriched event reaches the correct topic and schema version:
   asb.event.version=1.1.0
   asb.event.type=transactionsEnriched
   asb.event.source=gc-saltedge-position-keeping-inbound-connector
   asb.event.topic=transactions-enriched
   asb.producer.apiUri=http://asb-producer-v0.synchub-producer.svc.cluster.local
   
8. Store SaltEdge credentials and webhook secrets in a SOPS secret. For more information, see How to create SOPS.

​

Test your integration

1. Call POST {baseURL}/internal/transactions/enrichment with a test batch. The batch must include a unique enrichmentRequestId, a partyInformation array, and at least one entry in accounts.
2. Confirm Grand Central returns 202 with an empty body.
3. When SaltEdge sends the categorization callback to POST {baseInboundURL}/webhooks/transaction-categorizations, confirm the connector publishes transactionsEnriched to Sync Hub.
4. Verify downstream consumers receive the expected enrichment payload.

For operation and event details, see Reference. For the full contract, see API playground.

​

Troubleshooting

If the connector does not respond as expected, check these common scenarios.