Hanzo
OpenapiBilling

Reads one of the caller's own deposit intents back — pending, confirming, or…

Reads one of the caller's own deposit intents back — pending, confirming, or succeeded.

GET /v1/billing/crypto/deposit/{id}

Addresshttps://api.hanzo.ai/v1/billing/crypto/deposit/{id}
MethodGET
Operationget_billing_crypto_deposit_by_id
AuthAuthorization: Bearer $HANZO_API_KEY

Reads one of the caller's own deposit intents back — pending, confirming, or succeeded.

An intent belonging to another payer answers 404, exactly as an id that names nothing, so a guessed id cannot confirm that somebody else's deposit exists.

A named handler, not a closure, so zipdoc can lift this prose into the registry.

Request

1 field.

FieldInTypeRequiredDescription
idpathstringyesID is the deposit intent id.

Response

StatusBodyMeaning
200CryptoDepositok

200 body — 7 fields.

FieldInTypeAlwaysDescription
addressTagbodystring
chainbodystring
depositAddressbodystring
expiresAtbodystring
idbodystring
statusbodystring
tokenbodystring

Failure carries the platform error shape — see Errors.

Examples

hanzo billing crypto deposit get <id>

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page