These endpoints manage the on-chain addresses your participants deposit crypto into. A deposit address is a blockchain address that zerohash generates and owns on a participant's behalf — funds sent to it are credited to that participant's account. Together, these three endpoints let you create addresses, look them up, and reassign them.
For engineers and PMs, this is the entry point for crypto coming into zerohash. Before a participant can fund their account with a given asset, they need an address to send it to. You generate that address programmatically, hand it to the user (or your deposit UI), and monitor it over its lifecycle. The address is tied to a specific participant and asset, so incoming funds are attributed automatically.
Generates a new deposit address for a given participant and asset. You specify the participant_code (your platform or one of its customers) and the asset, with an optional account_label to route deposits to a specific sub-account (defaults to general). The response returns the newly created address along with its identifiers. This is the call behind "show me where to send my BTC."
Returns the deposit addresses associated with a participant, paginated. You can filter by asset to narrow to a single one, or use inactivity_interval to surface addresses that have been dormant for a given number of days — handy for address lifecycle management, reconciliation, and identifying stale addresses. Reach for this when you need to display, audit, or reconcile the addresses already in play.
Reassigns ownership of an existing address to a different participant. You provide the address, the blockchain it lives on, and the participant_code of the new owner. Use this when control of an address needs to move between participants in your infrastructure — for example when account ownership changes. It updates who an address belongs to rather than creating a new one.