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.
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.
Fee rule creation payload
Request payload for creating a fee rule
The fee schedule to apply when this rule matches
"550e8400-e29b-41d4-a716-446655440000"
Display name for the fee rule
1 - 100"BB Right-Side Rule"
Which transaction side this rule applies to
LEFT, RIGHT, ANY "RIGHT"
Evaluation priority (must be unique within the context; LEFT, RIGHT, and ANY rules share the same priority space)
x >= 00
Conditions that must all match for this rule to apply
50Successfully created fee 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.
A fee rule that maps transaction metadata to a fee schedule within a reconciliation context
Unique identifier for the fee rule
"550e8400-e29b-41d4-a716-446655440000"
Reconciliation context this rule belongs to
"550e8400-e29b-41d4-a716-446655440000"
Fee schedule applied when this rule matches
"550e8400-e29b-41d4-a716-446655440000"
Display name for the fee rule
"BB Right-Side Rule"
Which transaction side this rule applies to
LEFT, RIGHT, ANY "RIGHT"
Evaluation priority (lower numbers are evaluated first; LEFT, RIGHT, and ANY rules share the same priority space)
0
Conditions that must all match for this rule to apply
Creation timestamp in RFC 3339 format
"2025-01-15T10:30:00Z"
Last update timestamp in RFC 3339 format
"2025-01-15T10:30:00Z"