HiveFlow API
Authenticate with JWT or API keys, trigger flows over HTTP, and explore the full OpenAPI reference in Apidog, Swagger UI or Redoc.
Everything the dashboard does goes through the HiveFlow REST API (https://api.hiveflow.ai/api), and you can use it directly: trigger flows from your systems, manage resources programmatically, or build on top of the platform.
Authentication
| Method | Use case |
|---|---|
| Bearer token (JWT) | Web sessions — obtained on login. |
| API keys | Server-to-server — create them in Profile → API Keys and send them with your requests. |
| Trigger keys | Each HTTP trigger node has its own key embedded in the webhook URL. |
Trigger a flow over HTTP
Add a Trigger (or Flow Input) node to your flow, copy its webhook URL, and call it:
curl -X POST "https://api.hiveflow.ai/api/triggers/flow/<flowId>/<apiKey>" \
-H "Content-Type: application/json" \
-d '{"message": "New order #1234"}'The payload becomes the flow's input; the response contains the flow's output. This is also the mechanism Hive Apps use to call their linked flow.
Full API reference (Apidog / OpenAPI)
The complete reference — auth, flows, nodes, executions, agents, Hive Apps, skills, WhatsApp, MCP and more (126 endpoints) — is maintained as an OpenAPI 3.0 spec generated from the codebase. We manage it in Apidog, and you can consume it in the format you prefer:
- Live spec:
GET https://api.hiveflow.ai/api-docs-json— import this URL directly into Apidog, Postman or any OpenAPI tool. - Swagger UI:
https://api.hiveflow.ai/api-docs - Redoc:
https://api.hiveflow.ai/docs/redoc
Main tag groups: Autenticación, API Keys, Flujos, Nodos, Conexiones, Procesamiento, LLM, Triggers, WhatsApp, MCP, Extension.
Credits and limits
API-triggered executions consume the same credits and respect the same plan limits as the dashboard. Public endpoints are rate-limited per IP/key.