Skip to main content

Counterparty balances are 64-bit

· 2 min read

Counterparty balances are 64-bit​

balance.available and balance.pending on a counterparty were documented as int32. They are not bounded by the 32-bit range, and a counterparty balance can legitimately exceed 2,147,483,647 cents ($21,474,836.47). Both fields are now documented as int64.

If you generate a client from our OpenAPI document, regenerate it. A client built from the previous spec reads these fields into a 32-bit integer and will overflow or fail to deserialize a balance above that range. No API behavior changed — only the documented type.

The two fields also carried a minimum of 100, which was incorrect: a counterparty balance can be 0, and a zero balance is required before a counterparty can be deleted. That constraint is gone, so a generated client with response validation no longer rejects a zero or low balance.

Payouts are still capped at int32​

A single payout is limited to 2,147,483,647 cents. That limit is real and enforced — a larger amount is rejected. The payout amount field now documents the cap explicitly, so a generated client validates it before the request.

A counterparty holding more than that must be paid out across multiple payouts. If that is a problem for your integration, contact us.