Use this endpoint to update the fields of a specific fee rule by its identifier. If the referenced fee schedule changes, the caller must also be allowed to read that 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 fee rule.
Fee rule updates
Request payload for updating a fee rule
Updated fee schedule to apply when this rule matches
Updated display name for the fee rule
100"Updated Rule"
Updated transaction side
LEFT, RIGHT, ANY "LEFT"
Updated evaluation priority (must remain unique within the context)
x >= 0Updated conditions for this rule
50Successfully updated 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"