API & Developer Reference
Build against HUM with the OpenAPI contract, the developer docs, and the embeddable widget.
Everything in HUM is API-first — the console uses the same endpoints you can.
The developer docs
The developer documentation covers authentication, the call lifecycle, agents, numbers, SMS, webhooks, and integration patterns, with example requests.
OpenAPI
A curated OpenAPI spec (JSON and YAML) describes the customer-facing API surface — use it for review, client generation, and integration planning. A read-only Swagger reference is hosted alongside it.
Authentication model
Browser requests use your BlueHive SSO session. AI assistants and backend integrations use revocable hum_live_* API keys with an organization role plus explicit read/write scopes. Both authentication methods resolve the same tenant boundary and authorization checks.
Use the AI Agent Setup guide for the remote MCP server, which exposes named tools for the agent lifecycle on top of the full API. To run a background agent from your own systems — either by pointing a third-party webhook at a tokenized trigger URL, or by assigning a task to one agent with your API key — see Trigger AI Agents via API.
The embeddable widget
A drop-in widget lets you put an AI voice session on your own website, gated by per-widget keys, origin allowlists, and abuse protections — talk to us about enabling it for your account.