Create a reconciliation source
Use this endpoint to create a new reconciliation source under a specific context. Sources define where transaction data comes from for reconciliation.
Authorizations
Bearer token authentication (format: "Bearer {token}")
Headers
A unique identifier for tracing the request across services.
Optional idempotency key for safe retries. Matcher reads the key only from this header, and only when you send one. A request that carries a key only in X-Idempotency-Key or Idempotency-Key is refused with 400 (MTCH-0015), and nothing is processed. If the same key is sent again and the original request was already processed, the stored response is returned with X-Idempotency-Replayed: true. A malformed key returns 400, a key whose first request is still in progress returns 409, and an idempotency storage failure returns 500. These refusals are problem documents.
Path Parameters
The unique identifier of the reconciliation context. Context ID
Body
Source creation payload
Human-readable name of the source.
1 - 50"Primary Bank Account"
Matching side this source feeds. LEFT and RIGHT are the two sides reconciled against each other.
LEFT, RIGHT "LEFT"
Origin of the source data. LEDGER is the internal ledger; BANK is a bank statement feed; GATEWAY is a payment gateway; CUSTOM is a bespoke feed; FETCHER is a discovery-engine pull.
LEDGER, BANK, GATEWAY, CUSTOM, FETCHER "BANK"
Source-specific configuration object. Cross-key rules the schema cannot express: a duplicate_key component this source's field map does not fill is refused, because a key over an always-empty field makes every row a duplicate of every other; a source bound to an aggregator connection (reserved key connection_config_name) cannot carry a duplicate_key of its own, and a config holding both is refused in either direction; and editing duplicate_key governs later imports only — rows already imported keep the key they were deduplicated under, so a duplicate straddling the change is knowingly not detected.
Response
Successfully created source.
Source-specific configuration object. Cross-key rules the schema cannot express: a duplicate_key component this source's field map does not fill is refused, because a key over an always-empty field makes every row a duplicate of every other; a source bound to an aggregator connection (reserved key connection_config_name) cannot carry a duplicate_key of its own, and a config holding both is refused in either direction; and editing duplicate_key governs later imports only — rows already imported keep the key they were deduplicated under, so a duplicate straddling the change is knowingly not detected.
Identifier of the context this source belongs to.
"550e8400-e29b-41d4-a716-446655440000"
Creation timestamp in RFC 3339 format.
"2025-01-15T10:30:00Z"
Unique identifier of the source.
"550e8400-e29b-41d4-a716-446655440000"
Human-readable name of the source.
"Primary Bank Account"
Matching side this source feeds. LEFT and RIGHT are the two sides reconciled against each other.
LEFT, RIGHT "LEFT"
Origin of the source data. LEDGER is the internal ledger; BANK is a bank statement feed; GATEWAY is a payment gateway; CUSTOM is a bespoke feed; FETCHER is a discovery-engine pull.
LEDGER, BANK, GATEWAY, CUSTOM, FETCHER "BANK"
Last update timestamp in RFC 3339 format.
"2025-01-15T10:30:00Z"
RFC 3339 timestamp when the source was archived; absent when the source is live.
"2025-01-15T10:30:00Z"

