Skip to main content
POST
Release group balance
Moves funds from HELD back to AVAILABLE for a group, making them spendable again. Use this to reverse authorization holds or complete approval workflows on a shared wallet. The operation is program-scoped: program_id is required in the body along with asset_id and a description. If amount is omitted, all held funds for the specified asset are released. For LOT mode assets, you can narrow the scope with lot_ids, earned_from, earned_to, or reference_id to target specific lots.

Release by reference_id

When reference_id is provided, only lots stamped with that reference during a previous hold are targeted. This enables precise release of specific holds when a group has multiple concurrent holds. Releases behave the same way on group and participant wallets; see release participant balance for the participant equivalent.
For usage patterns and examples, see the Balance Operations guide. For group wallets in general, see the Groups guide.

Authorizations

X-API-Key
string
header
required

API key passed in the X-API-Key header.

Headers

Idempotency-Key
string

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.

Maximum string length: 255

Path Parameters

id
string<uuid>
required

Group ID

Body

application/json

Release parameters

asset_id
string<uuid>
required

Asset to operate on

Example:

"550e8400-e29b-41d4-a716-446655440001"

description
string
required

Reason for this operation

Required string length: 1 - 500
Example:

"Hold for pending order #123"

program_id
string<uuid>
required

Program this operation belongs to

Example:

"550e8400-e29b-41d4-a716-446655440000"

amount
string

Amount to process. Omit to process the full balance (SIMPLE) or all matching lots (LOT)

Example:

"100.00"

bucket
enum<string>

Which bucket to forfeit from. Required for forfeit; ignored for hold/release

Available options:
AVAILABLE,
HELD
Example:

"AVAILABLE"

earned_from
string<date-time>

Only process lots earned on or after this time (RFC 3339). LOT mode only.

Example:

"2024-01-01T00:00:00Z"

earned_to
string<date-time>

Only process lots earned on or before this time (RFC 3339). LOT mode only. Must be >= earned_from when both are provided.

Example:

"2024-12-31T23:59:59Z"

idempotency_key
string

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.

Required string length: 1 - 255
Example:

"order-123-hold"

lot_ids
string[]

Restrict to specific lots. LOT mode only

Example:
reference_id
string

Correlation ID linking holds to releases. LOT mode only. Hold stamps lots; release filters by reference.

Example:

"auth_12345"

Response

Balance released

amount_processed
string

Total amount processed

Example:

"100.00"

asset_id
string<uuid>

Asset ID

Example:

"550e8400-e29b-41d4-a716-446655440001"

balance
object

Balance after the operation

journal_entry_id
string<uuid>

Ledger journal entry created by this operation

Example:

"550e8400-e29b-41d4-a716-446655440003"

lots_processed
object[]

Individual lots affected. Only present for LOT mode assets

message
string

Confirmation message

Example:

"Processed 100.00"

operation
string

Operation performed

Example:

"HOLD"

program_id
string<uuid>

Program ID

Example:

"550e8400-e29b-41d4-a716-446655440000"

reference_id
string

Correlation ID linking this hold/release (if provided)

Example:

"auth_12345"