The Wireflow API lets you execute AI workflows programmatically, poll for results, and manage resources using standard REST calls with Bearer-token authentication.

Base URL

https://www.wireflow.ai/api/v1

Section index

• Overview — architecture, pagination, idempotency
• Authentication — API keys, scopes, rotation
• Workflows — list, get, create, update, delete
• Nodes — the node catalog: ports, config keys, enum options, defaults, pricing. The source of truth for building graphs
• Templates — discover published templates (metadata + input interface, never the graph)
• Execute Templates — run a template by reference on your own credits
• Video Compositions (what a Video Editor node expects: template inputMappings and the sceneGraph authoring contract)
• Run — trigger an execution
• Executions — poll status, fetch outputs, list history
• Webhooks — push-based triggers without OAuth
• Publishing — publish a workflow as a branded app
• Rate limits — per-plan limits and retry headers
• Errors — error codes and recovery patterns

Quick start

Execute a workflow and poll for results:

# 1. Fire an execution — returns executionId immediately
curl -X POST https://www.wireflow.ai/api/v1/workflows/YOUR_WORKFLOW_ID/execute \
  -H "Authorization: Bearer sk-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{"inputs": {"prompt": "a neon city at night, cinematic"}}'

# 2. Poll until complete
curl https://www.wireflow.ai/api/v1/workflows/executions/EXEC_ID \
  -H "Authorization: Bearer sk-your-api-key"

Discovery

• OpenAPI spec: /.well-known/api-catalog (RFC 9727 linkset)
• Agent skills index: /.well-known/agent-skills/index.json (Cloudflare RFC v0.2.0)
• MCP server card: /.well-known/mcp/server-card.json — see MCP integration
• Public node catalog: GET /api/v1/nodes — unauthenticated, every wireable node with ports, config keys, enums, and pricing. Use this to build graphs; docs
• Public model catalog: GET /api/v1/models — unauthenticated, returns every model with credit cost. For building graphs use /nodes
• Identity check: GET /api/v1/me — which account your API key acts as (userId, email, plan). Call it before writes when running multiple keys or agents

Client libraries

Official clients land in 2026 Q2. Meanwhile, any HTTP client works — the API surface is intentionally small (9 endpoints to know) and uses only Bearer-token auth plus JSON request/response bodies.

Support

• Email: [email protected]
• Discord: discord.com/invite/KGatnxrETG