Build on Flowie, the agentic Finance & Procurement orchestration platform. This is the canonical entry point for every Flowie developer resource — the Flowie Exchange REST API, its OpenAPI 3.1 specification, the Flowie MCP server for AI agents, webhooks and events, and how to authenticate. Every resource lives at a stable, predictable URL so both people and agents can find it by name.
Flowie API documentation
The Flowie Exchange API is one REST API for sending and receiving invoices, resolving companies, running compliance across 47+ countries, and orchestrating Finance & Procurement workflows.
- Human API reference: docs.get-flowie.com/reference
- Docs home: docs.get-flowie.com
- Production base URL:
https://back.p2p-flowie.com/exchange - Sandbox base URL:
https://back.flowie.ink/exchange
Flowie OpenAPI 3.1 specification
The complete, machine-readable description of the Flowie Exchange API — every endpoint, schema, and security scheme — as OpenAPI 3.1.
- OpenAPI spec (JSON): get-flowie.com/openapi.json
- API catalog (RFC 9727 linkset): get-flowie.com/.well-known/api-catalog
Point any OpenAPI-aware client, SDK generator, or function-calling agent at the spec URL to generate typed bindings.
Flowie authentication
The Flowie Exchange API uses a Bearer token in the Authorization header:
an OAuth access token from signing in with your Flowie login (SSO included;
dynamic client registration and PKCE supported), or an Exchange API key
(flw_live_…, flw_test_… for sandbox) for integrations. An AI assistant
should sign in through MCP. It does not need an API key.
- Auth walkthrough for agents: get-flowie.com/auth.md
- Protected-resource metadata (RFC 9728): get-flowie.com/.well-known/oauth-protected-resource
- MCP setup, copy-ready: docs.get-flowie.com/mcp.md
- API keys (integrations): created in the Flowie app by an organization admin; sandbox keys need no signup. Otherwise, ask the Flowie team.
Flowie MCP server (for AI agents)
Connect Claude, ChatGPT, Cursor, VS Code or Claude Code to Flowie over the Model Context Protocol (MCP). Add the URL and sign in with your normal Flowie login. There is no API key to request. Copy-ready configuration: docs.get-flowie.com/mcp.md.
-
App server (most people want this one):
https://back.p2p-flowie.com/agent-hub/mcp. The Flowie app as tools (purchase requests, approvals, tasks, budgets, flows, payments), acting as the signed-in user. Sign-in only. Staging:https://back.flowie.ink/agent-hub/mcp. -
Exchange API server (for integrations):
https://back.p2p-flowie.com/exchange/mcp. E-invoicing send/receive/validate/lifecycle, companies, partners, directory. Sign-in or an API key. Staging:https://back.flowie.ink/exchange/mcp. -
Claude Code:
claude mcp add --transport http flowie-app https://back.p2p-flowie.com/agent-hub/mcp, then/mcp→ Authenticate. -
Public content MCP (read-only, no auth):
https://get-flowie.com/mcp— toolssearch_flowie,fetch_flowie_page,get_flowie_overview. -
MCP server card: get-flowie.com/.well-known/mcp/server-card.json
-
Documentation MCP server:
https://docs.get-flowie.com/mcp -
Agent skills: get-flowie.com/.well-known/agent-skills/index.json
-
Agentic Resource Discovery (ARD) catalog: get-flowie.com/.well-known/ard.json — one manifest listing every Flowie agentic resource (MCP server, OpenAPI spec, agent skill, API catalog).
Flowie webhooks & events
Subscribe to real-time events (document status, delivery, lifecycle) instead of polling. Webhooks and an events feed are part of the Exchange API.
- Webhooks:
POST /v1/webhooks— register endpoints (see the API reference). - Events feed:
GET /v1/events, with acknowledge (/v1/events/ack) and replay (/v1/events/{event_id}/replay).
Machine-readable everything
Every page on get-flowie.com is available as clean Markdown for agents — append
.md to any path (e.g. get-flowie.com/platform/ai-agents.md)
or send Accept: text/markdown. See also the site indexes
llms.txt and
llms-full.txt, and the agent guide
agents.md.
Last updated: 2026-08-06