Pricing
Apps
Log inStart free trial

API changelog & versioning

How WEXTL's REST API versions over time, and what "frozen-additive" means for your integration.

The REST API is versioned by URL prefix (/api/v1, and eventually /api/v2). v1 is frozen-additive: existing fields, endpoints, and behavior never change or disappear — only new, optional fields and new endpoints are added. A pinned integration built against v1 today keeps working indefinitely.

A genuinely breaking change (removing a field, changing a type, altering existing behavior) ships as a new version prefix instead of mutating v1 — you opt in by changing the URL, on your own schedule.

New entries are appended to the top of this list as the v1 surface grows — additive changes (new fields, new endpoints) do not get their own entry unless they introduce a new resource.

  • 2026-08-02 — Added databases, credentials, structures, functions, teams, and webhooks resources; organization activity and invitations exposed over REST and MCP.
  • 2026-08-01 — v1 launch: the REST API (workflow CRUD, headless graph-apply, deploy), the /api/mcp MCP server, and the @wextl/sdk TypeScript SDK on npm.