Hold group balance
Moves group balance from AVAILABLE to HELD. The asset must be ACTIVE; archived assets reject new holds.
AVAILABLE to HELD for a group. Held funds are not spendable and remain reserved until explicitly released or forfeited. Common use cases include authorization holds, pending redemptions, and approval workflows on a shared wallet.
Groups are organization-level ledger entities, but every balance operation is program-scoped: program_id is required in the body along with asset_id and a description. The hold fails if the group does not have sufficient AVAILABLE balance. For assets in LOT mode, hold operations preserve lot-level metadata such as expires_at and matures_at, and you can restrict the hold to specific lots with lot_ids, earned_from, or earned_to.
Hold/Release Correlation (reference_id)
For LOT mode assets, you can include an optional reference_id to correlate this hold with a future release. Held lots are stamped with the reference, and a subsequent release using the same reference_id targets only those lots. This is useful when a group has multiple concurrent holds.
- Format: 1-255 characters, alphanumeric plus
._:@- - Only supported on
LOTmode assets - Not supported for forfeit operations
Authorizations
API key passed in the X-API-Key header.
Headers
Idempotency key (1-255 printable ASCII chars). Equivalent to the idempotency_key body field; if both are provided they must match. Replays with the same key and identical parameters return the original result; the same key with different parameters returns 409 idempotency_conflict.
255Path Parameters
Group ID
Body
Hold parameters
Asset to operate on
"550e8400-e29b-41d4-a716-446655440001"
Reason for this operation
1 - 500"Hold for pending order #123"
Program this operation belongs to
"550e8400-e29b-41d4-a716-446655440000"
Amount to process. Omit to process the full balance (SIMPLE) or all matching lots (LOT)
"100.00"
Which bucket to forfeit from. Required for forfeit; ignored for hold/release
AVAILABLE, HELD "AVAILABLE"
Only process lots earned on or after this time (RFC 3339). LOT mode only.
"2024-01-01T00:00:00Z"
Only process lots earned on or before this time (RFC 3339). LOT mode only. Must be >= earned_from when both are provided.
"2024-12-31T23:59:59Z"
Client-provided key to dedupe retries. May also be supplied via the Idempotency-Key HTTP header; when both are present they must match. Identical operations with the same key return the original result; a reused key with different payload returns 409 idempotency_conflict.
1 - 255"order-123-hold"
Restrict to specific lots. LOT mode only
Correlation ID linking holds to releases. LOT mode only. Hold stamps lots; release filters by reference.
"auth_12345"
Response
Balance held
Total amount processed
"100.00"
Asset ID
"550e8400-e29b-41d4-a716-446655440001"
Balance after the operation
Ledger journal entry created by this operation
"550e8400-e29b-41d4-a716-446655440003"
Individual lots affected. Only present for LOT mode assets
Confirmation message
"Processed 100.00"
Operation performed
"HOLD"
Program ID
"550e8400-e29b-41d4-a716-446655440000"
Correlation ID linking this hold/release (if provided)
"auth_12345"