REST API
Build integrations with Innflow workflows, executions and workspaces
Use the Innflow REST API to create and import workflows, deploy them, start executions and read results. The API also exposes graph authoring, node schemas and connected-account discovery.
Base URL
https://app.innflow.ai/api/v1Browse all 25 operations · Download OpenAPI 3.1 · CLI reference
Make your first request
Create a key in Settings → API Keys. The full key is shown once. Store it on your server or in your shell environment as INNFLOW_API_KEY.
curl 'https://app.innflow.ai/api/v1/workspaces' \
--header "Authorization: Bearer $INNFLOW_API_KEY"List workflows in your personal workspace (select it explicitly):
curl 'https://app.innflow.ai/api/v1/workflows?page=1&pageSize=20' \
--header 'X-Innflow-Workspace: personal' \
--header "Authorization: Bearer $INNFLOW_API_KEY"To select an organization, add X-Innflow-Workspace with an organization ID returned by List workspaces. See authentication, permissions and errors.
Start a workflow and read its result
Choose a configured, deployed workflow. Replace workflow_id with its ID. Give each new execution a unique idempotency key; reuse that key only when retrying the same request.
curl --request POST 'https://app.innflow.ai/api/v1/workflows/workflow_id/execute' \
--header "Authorization: Bearer $INNFLOW_API_KEY" \
--header 'Content-Type: application/json' \
--header 'Idempotency-Key: customer-onboarding-001' \
--data '{"input":{"email":"customer@example.com"}}'The response's data.executionId identifies the asynchronous run. If several triggers are eligible, include triggerNodeId in the request body.
curl 'https://app.innflow.ai/api/v1/executions/execution_id?view=summary' \
--header "Authorization: Bearer $INNFLOW_API_KEY"Poll with backoff until the execution finishes. Use execution logs for node-level diagnostics and execution payload for chunked output.
API areas
| Area | What you can do |
|---|---|
| Workspaces | Discover the workspaces you can access |
| Workflows | Create, import, inspect, update, duplicate, deploy and delete workflows |
| Executions | Start runs, inspect status, read logs and retrieve output |
| Authoring | Edit graphs, validate configuration and configure triggers |
| Catalog | Discover node types, fields, connected accounts and operation receipts |
OpenAPI and client tooling
Download the complete documentation OpenAPI snapshot to import into API clients. It uses the absolute production API base URL and describes the request parameters and bodies for all 25 documented operations.
The application also serves its own OpenAPI document. That document currently covers a smaller core subset. The documentation snapshot includes the additional routes reviewed on September 28, 2026. Response bodies are described per endpoint; the snapshot does not promise exhaustive typed response models.
Supported surface
These pages describe the customer REST routes under /api/v1. Authoring availability is deployment-dependent; check authoring context before editing graphs. Workflow webhooks and MCP have their own setup guides. Internal service endpoints and browser-session APIs are not customer REST contracts.
Workflow layout metadata
Workflow definitions can carry canvasLayoutVersion alongside nodes and connections. Version 0 identifies a definition eligible for the editor’s one-time horizontal arrangement; version 1 identifies one already using that layout version. Imports default to 0, new workflows start at 1, and duplicates preserve the value. Preserve this field across exports and imports. It tracks canvas arrangement separately from execution version or deployment state.