Use this endpoint to create a new match rule within a specific context. Match rules define how transactions are matched during reconciliation.
Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
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.
The unique identifier of the reconciliation context.
Match rule creation payload
Successfully created match rule.
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.
Matching rule within a reconciliation context
Rule configuration
Context ID this rule belongs to
"019c96a0-10a0-72d2-9fb0-2b7de8093182"
Creation timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"
Unique identifier for the rule
"019c96a0-1071-7a0d-9916-a831221de252"
Execution priority (lower = higher priority)
1 <= x <= 10001
Type of matching rule
EXACT, TOLERANCE, DATE_LAG "EXACT"
Last update timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"