Get started
Test & live mode
There is a single base URL for both environments. The mode is decided entirely by which secret you authenticate with — just like Stripe or Razorpay.
One URL, two secrets
You do not point at a different host for sandbox versus production. You authenticate with a test secret or a live secret, and the access token you receive is bound to that mode.
| Secret prefix | Mode | Use |
|---|---|---|
hpr_test_… | test | Development & integration against the sandbox |
hpr_live_… | live | Production traffic against the live catalog |
Key points
- The mode is echoed in the token response (
mode) and on every authenticated response as theX-Hoopr-Modeheader. - Your access token is bound to the mode of the secret that minted it — a test token can never read live data and vice-versa.
- To switch environments, authenticate with the other secret. Do not change the URL.
- Keep
hpr_live_…server-side and well-guarded; treat it like any production credential.
One URL, switch by secret
Never branch your code on the host. The base URL is identical in test and live — the only thing that changes is which secret (hpr_test_… or hpr_live_…) you exchange for a token.
Confirm the mode on every response
Every authenticated response carries the mode so you can assert you are talking to the environment you expect:
X-Hoopr-Mode: test