Environments and API Keys
Hum provides separate Sandbox and Production environments with the same API surface.
| Environment | Base URL | Purpose |
|---|
| Sandbox | https://api-sandbox.letshum.com | Integration development and testing |
| Production | https://api.letshum.com | Live traffic |
Build and test your integration against Sandbox before switching to Production.
Get an API Key
API keys are issued by Hum for each environment. There is no self-serve key dashboard. Request keys from your Hum contact or email support@letshum.com.
Keys are environment-specific and visibly prefixed:
- Sandbox:
hum_sandbox_XXXXXXXXXXXXXXXXXXXXXXXXXX
- Production:
hum_XXXXXXXXXXXXXXXXXXXXXXXXXX
A key works only in the environment that issued it. A Sandbox key cannot authenticate against Production, and a Production key cannot authenticate against Sandbox.
Verify Your Key
Use GET /ping as the first authenticated request:
curl https://api-sandbox.letshum.com/ping \
-H "Authorization: Bearer hum_sandbox_XXXXXXXXXXXXXXXXXXXXXXXXXX"
{
"message": "🎤 We're humming along!",
"timestamp": "2026-07-13T16:26:17.874Z"
}
After this succeeds, continue with API Integration.
API Reference Playground
The API Reference Try it playground defaults to the Sandbox server because Sandbox is listed first in the API specification. If you use a Production key without changing the server selector to Production, the request returns HTTP 401.