gc-saltedge-position-keeping-connector, orchestrates SaltEdge Data Enrichment processing. The inbound connector, gc-saltedge-position-keeping-inbound-connector, receives the SaltEdge callback and publishes the results to Sync Hub. For setup steps, see Get started.
Configuration properties
Values to obtain from the vendor
Obtain the following values from SaltEdge and set them in the connector values files for your runtime. The following table lists each property and its purpose.gc-saltedge-position-keeping-inbound-connector
The following table lists the deployment properties of the inbound connector,gc-saltedge-position-keeping-inbound-connector, and the values that Grand Central ships as defaults.
gc-saltedge-position-keeping-connector
The following table lists the deployment properties of the outbound connector,gc-saltedge-position-keeping-connector.
SOPS secrets
Both connectors send the SaltEdgeApp-Id and App-Secret as request headers. The following table lists the credentials to store in a SOPS secret. For more information, see How to create SOPS.
Supported operations
For the full contract, see the API playground.Inbound webhook
An enrichment request must include a unique
enrichmentRequestId, a partyInformation array, and an accounts array. A request can contain a maximum of 50 accounts, and each account can contain a maximum of 100 transactions.
Events
gc-saltedge-position-keeping-inbound-connector
The inbound connector publishes the following Sync Hub events when SaltEdge categorization completes.
Published events use the standard Grand Central envelope. The
data payload includes per-transaction category, merchant, location, and counterparties.
The inbound connector publishes an event only when the SaltEdge callback reports a completed categorization. For any other callback status, the inbound connector acknowledges the callback and publishes no event.