Authentication

Create an API key in the dashboard and send it as X-API-Key or Authorization: Bearer. Keys carry buy and scrape scopes plus an optional daily spend cap.

Create an API key in your dashboard under Settings → API keys. The full key (prefixed hpx_) is shown once at creation, so store it somewhere safe. Send it on every request in the X-API-Key header, or as a Bearer token, both are accepted, same as Stripe or OpenAI.

Both headers work

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

# Authorization: Bearer also works
curl https://hproxy.com/api/v1/wallet \
  -H "Authorization: Bearer hpx_your_key_here"

Scopes

Each key carries scopes that gate what it can do. A key missing the required scope gets a 403 with code missing_scope.

Field	Type	Description
`buy`	scope	Create orders and deposits; read wallet, plans, orders and your proxies; generate lines; manage webhooks.
`scrape`	scope	Run the data scrapers. Independent of buy, so a scrape key can't place orders.

Daily spend cap

Each key can carry an optional daily spend cap. If a key's orders in the last 24h would exceed the cap, the next order is refused with 402 before any charge, so a leaked key can't drain your balance.

Keep your keys secret

Keep keys server-side. Never ship them in client code. Lost a key? Revoke it and create a new one in Settings → API keys.

← Previous

Quickstart

Rate limits & retries

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