Flowline Public API
A read-only REST API for Flowline's plans, documentation and product information — for AI agents, scripts and integrations. No API key needed.
Overview
The Flowline public API lives under https://flowlineworkspace.com/api/v1. Every endpoint is a GET that returns JSON, needs no authentication and allows cross-origin requests. The full machine-readable description is the OpenAPI 3.1 document at /openapi.json; an index of the whole site for AI agents is at /llms.txt.
No user data yet
The public API does not read or change anyone's tasks, habits or calendar. Agent integrations with access to your own Flowline data are on the roadmap.
Endpoints
| Option | Description |
|---|---|
| GET /api/v1/plans | Every plan (Free, Plus, Pro): prices in EUR, free trial and features. |
| GET /api/v1/plans/{planId} | One plan by id — free, plus or pro. |
| GET /api/v1/docs | Every documentation page: title, summary, section and URL. |
| GET /api/v1/product | What Flowline does: features, roadmap and useful links. |
The public pages also answer Accept: text/markdown with a Markdown version: the homepage, /pricing, /docs, /about and /contact.
Versioning and deprecation
The version is in the path (/api/v1). Within a version, changes are additive only: new endpoints or new fields, never a removed or renamed one. A breaking change ships as a new version (/api/v2) next to the old one.
A deprecated endpoint keeps working for at least six months and announces it on every response with a Deprecation header (RFC 9745), a Sunset header with the removal date (RFC 8594) and a Link to its successor. Today that is /api/plans, replaced by /api/v1/plans and removed after 2027-04-30.
Errors
Errors use the problem details format of RFC 9457 (application/problem+json): type, title, status, detail, plus a stable machine-readable code.
not_found — 404
The endpoint or the resource (for example an unknown plan id) does not exist.
rate_limited — 429
Too many requests. Wait the number of seconds in Retry-After, then retry.
internal_error — 500
Something failed on our side. Retry later; it is safe, every endpoint is read-only.
Rate limits
Each client IP can make 60 requests per 60 seconds. Every response says where you stand, so you can throttle yourself:
| Option | Description |
|---|---|
| RateLimit-Policy | The policy: "default";q=60;w=60 — quota and window in seconds (IETF RateLimit header fields). |
| RateLimit | What is left: "default";r=<remaining>;t=<seconds until reset>. |
| RateLimit-Limit / -Remaining / -Reset | The same numbers as separate headers, for older clients. |
| Retry-After | On a 429 only: seconds to wait before retrying. |