v1 overview
The REST API lets you create workflows, run them, and inspect run history from any HTTP client. Every route lives under a single versioned prefix and returns a consistent JSON envelope — see Errors & rate limits for the shape.
The full per-resource reference below — every endpoint, its parameters, request/response schemas, and a runnable curl + TypeScript SDK sample — renders directly from the machine-readable OpenAPI document at the path below, so it can never drift from what actually ships.
Machine-readable spec
The full contract is published as an OpenAPI document once the v1 surface ships, at the path below — unauthenticated, so your tooling (or an AI agent) can fetch it with no token.[3]
GET /api/v1/openapi.jsonAuthenticating requests
Every v1 request carries a bearer Personal Access Token or an OAuth 2.1 access token. See the Authentication guide for the full scope model and a key-rotation recipe.
References
- WEXTL® REST v1 API — our own source implementation.
- Our users' real API integrations and automations.
- The machine-readable OpenAPI specification for the REST API.