Account & wallet

GET /me verifies a key, GET /wallet reads your balance in integer cents, POST /deposits tops it up by card or crypto.

The shared plumbing every integration uses: verify a key, read the wallet that pays for both proxy orders and scraper calls, and top it up. Money is always integer cents.

GET/api/v1/me

Who am I

The fastest check that a key works. Accepts any valid key (no scope needed) and echoes the account it acts for plus the scopes the key carries.

curl https://hproxy.com/api/v1/me -H "X-API-Key: hpx_your_key_here"

GET/api/v1/wallet

Get wallet

Your current wallet balance, in integer cents.

curl https://hproxy.com/api/v1/wallet -H "X-API-Key: hpx_your_key_here"

POST/api/v1/deposits

Top up wallet

Add funds to your wallet. Returns a hosted payUrl to complete the payment by card or crypto. Amount is in cents.

Parameter	Type	Required	Description
`amount_cents`	integer	required	Amount to add, in cents. Sub-minimum top-ups are bumped to the method floor.
`method`	string	optional	"card" (default) or "crypto".

curl -X POST https://hproxy.com/api/v1/deposits \
  -H "X-API-Key: hpx_your_key_here" \
  -H "Idempotency-Key: deposit-2026-07-11-001" \
  -H "Content-Type: application/json" \
  -d '{"amount_cents":5000,"method":"crypto"}'

← Previous

Errors

OpenAPI spec

Need a hand wiring this up? Email [email protected]. A real person reads every message.