BioFlow / Developers
A public REST API, signed webhooks, an open-source TypeScript SDK, and a remote MCP server for AI agents — one API key, one coherent docs surface, live at https://app.getbioflow.com/v1.
curl "https://app.getbioflow.com/v1/pages" \
-H "Authorization: Bearer bf_live_YOUR_KEY"GET /v1/contacts pages through every newsletter signup, form submission, and gated download — or skip polling and subscribe to contact.created webhooks.
POST /v1/pages, add blocks, then the two-phase publish — draft first, nothing goes live until you say so. Idempotency keys make retries safe.
GET /v1/analytics/summary: views, clicks, unique visitors, CTR, top links, referrers, and tip revenue over 7/30/90 days.
sale.paid and sale.refunded events, signed per Standard Webhooks v1, with retries, rotation, and replay — all manageable over the API.
GET /v1/files lists uploaded files with public paths, ready to drop into image, carousel, or product blocks.
GET /v1/usage reports quota consumption and is free — it never counts against your monthly quota.
Types generated from the same OpenAPI 3.1 spec the API serves, a typed RFC 9457 error class per problem code, automatic retries with auto-generated idempotency keys, cursor-pagination iterators, and verifyWebhook for Standard Webhooks v1.
The npm package is landing shortly — until then, the SDK builds from source. The GitHub README has the current install path.
The API is plain REST + JSON — every operation page shows a runnable cURL and TypeScript fetch example, and the whole surface is described by one OpenAPI 3.1 document if you prefer to generate your own client.
Claude, ChatGPT, Copilot, or any MCP client can operate a workspace through OAuth 2.1 — read analytics, edit drafts, and (only with an explicit toggle plus a two-step confirm) publish. Full docs on /mcp.
claude mcp add --transport http bioflow https://app.getbioflow.com/api/mcpEvery docs page has a markdown twin at {page-url}.md (see AI tooling). Paste this to get an assistant productive immediately:
You're helping me build on the BioFlow API. Read https://getbioflow.com/docs/api.md for the full surface (auth, quotas, errors, all 22 operations), then help me write code against https://app.getbioflow.com/v1. My API key is in the BIOFLOW_API_KEY env var — never print it.| Plan | Monthly quota | Per-key burst |
|---|---|---|
| Free | — (no API access) | — |
| Creator | 10,000 requests/mo | 60 requests/min |
| Pro | 100,000 requests/mo | 120 requests/min |
The quota counts successful /v1 requests per calendar month; GET /v1/usage is free. Responses carry IETF draft-11 RateLimit headers, so your client always knows where it stands. Full plan details on /pricing.
Standard Webhooks v1 signing, the event catalog with payloads, the retry ladder, and replay.
Read the guide →The machine-readable description of all 22 operations — generate clients, mock servers, tests.
Download openapi.json →The whole API reference as plain text for AI assistants — plus the compact /llms.txt index.
Open llms-full.txt →Dated platform updates with an RSS feed — what shipped, when, and what changed.
See the changelog →Self-serve a key and make your first call in a minute — or read the docs end-to-end first. Both paths land in the same place.