Use this endpoint to create a new reconciliation context. Contexts are used to scope matching rules and organize your reconciliation configuration.
Bearer token authentication (format: "Bearer {token}")
A unique identifier for tracing the request across services.
Optional idempotency key for safe retries. Also accepts Idempotency-Key as an alternative header name. If the same key is sent again and the original request was already processed, the cached response is returned with X-Idempotency-Replayed: true.
See Retries and idempotency for details.
Context creation payload
1 - 100"Bank Reconciliation Q1"
Reconciliation topology (cardinality between sources)
1:1, 1:N, N:M "1:1"
1 - 100"daily"
Fee rate identifier to associate with this context
"019c96a0-2b20-7123-9a1b-2c3d4e5f6a7b"
Absolute fee tolerance amount
"0.01"
Percentage fee tolerance
"0.5"
Fee normalization mode
NET, GROSS "NET"
Whether to trigger matching automatically after file upload
false
Successfully created context.
The response includes the X-Idempotency-Replayed header.
If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request.
See Retries and idempotency for more details.
"019c96a0-10a0-72d2-9fb0-2b7de8093182"
"019c96a0-0a98-7287-9a31-786e0809c769"
"Bank Reconciliation Q1"
Reconciliation topology (cardinality between sources)
1:1, 1:N, N:M "daily"
Lifecycle status of a reconciliation context
DRAFT, ACTIVE, PAUSED, ARCHIVED "019c96a0-2b20-7123-9a1b-2c3d4e5f6a7b"
"0"
"0"
NET, GROSS "NET"
false
"2026-02-02T13:37:55Z"
"2026-02-02T13:37:55Z"