Skip to main content

​
Environments and API Keys

Hum provides separate Sandbox and Production environments with the same API surface.
Build and test your integration against Sandbox before switching to Production.
Sandbox serves the same national provider data set as Production, including the same data-set version. Use any real US address for testing; the example addresses in these docs work in Sandbox. An empty result means that no providers cover the address, just as it does in 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.

​
Widget Environments

Use the bundle and key for the same environment:
The hosted WebView page at https://webview.letshum.com loads the Production widget bundle, so it requires a Production key.

​
Verify Your Key

Use GET /ping as the first authenticated request:
cURL
Response
After this succeeds, continue with API Integration.

​
Postman

Prefer Postman? Import the ready-made collection. See Postman Collection.

​
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.