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.

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.

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 — either an Exchange API key (flw_live_…, flw_test_… for sandbox) or a Flowie JWT issued by Flowie's Auth0 tenant.

Flowie MCP server (for AI agents)

Flowie ships a Model Context Protocol (MCP) server so agents in Claude, ChatGPT, and other runtimes can call Flowie natively over Streamable HTTP.

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