Hanzo
OpenapiBilling

Add funds with a card already on file

Charges a saved card and credits the caller's prepaid wallet.

POST /v1/billing/topup

Addresshttps://api.hanzo.ai/v1/billing/topup
MethodPOST
Operationpost_billing_topup
AuthAuthorization: Bearer $HANZO_API_KEY

Charges a saved card and credits the caller's prepaid wallet.

The method must belong to the caller: one that does not is NOT FOUND rather than refused, so an id cannot be probed for existence. A saved row whose card is no longer chargeable is 422 — add the card again — which is a different thing to do than a decline (402) or a bad amount (400).

Retries behave exactly as they do for a token top-up: same key, same replay, same exactly-once at the processor.

Request

The document declares no body for POST /v1/billing/topup. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_billing_topup, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo billing topup create

Billing API · All Hanzo APIs · Interactive reference

How is this guide?

On this page