API Overview
OrcFlows exposes a JSON REST API served by cmd/api (default http3001). This section documents the raw HTTP API; for narrative/conceptual documentation of what each resource does, see Core Concepts.
Authentication
Register
Workflows
CRUD, lifecycle, and triggering for workflow definitions. All routes are under /api/v1/workflows and require a JWT.
Executions & Approvals
Routes for inspecting, controlling, and signaling running and completed executions. All routes are under /api/v1 and require a JWT.
Public & Webhook Routes
These routes require no JWT. Each is protected by its own mechanism — an unguessable workflow UUID, a workflow-scoped API key, or a provider signature — described per route.
Other Resources
Quick reference for the remaining /api/v1 resources. Each links to the Core Concepts page with full conceptual detail and field tables.