Create a fee rule
Use this endpoint to create a new fee rule that maps transaction metadata to a fee schedule within a context.
Priority must be unique within a context across all sides (LEFT, RIGHT, and ANY rules share the same priority space). The caller must also be allowed to read the referenced fee schedule.
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
Fee rule creation payload
UUID of the fee schedule this rule applies when its predicates match.
"550e8400-e29b-41d4-a716-446655440000"
Human-readable name of the fee rule.
1 - 100"BB Right-Side Rule"
Predicates (ANDed together) that a transaction's metadata must satisfy for this rule to apply.
Evaluation priority; lower numbers are evaluated first. Must be unique within the context. LEFT, RIGHT, and ANY rules share the same priority space.
0
Side the rule applies to. LEFT and RIGHT target one reconciliation side; ANY matches transactions on either side.
LEFT, RIGHT, ANY "RIGHT"
Response
Successfully created fee rule.
Identifier of the context the rule belongs to.
"550e8400-e29b-41d4-a716-446655440000"
Creation timestamp in RFC 3339 format.
"2025-01-15T10:30:00Z"
Identifier of the fee schedule this rule applies.
"550e8400-e29b-41d4-a716-446655440000"
Unique identifier of the fee rule.
"550e8400-e29b-41d4-a716-446655440000"
Human-readable name of the fee rule.
"BB Right-Side Rule"
Predicates (ANDed together) that a transaction's metadata must satisfy for this rule to apply.
Evaluation priority; lower numbers are evaluated first.
0
Side the rule applies to. LEFT and RIGHT target one reconciliation side; ANY matches transactions on either side.
LEFT, RIGHT, ANY "RIGHT"
Last update timestamp in RFC 3339 format.
"2025-01-15T10:30:00Z"

