Overview
REST API, CLI, MCP server, and an interactive API Explorer for building on SaaSFlow data.
Four ways to read and write SaaSFlow data programmatically. For a one-page tour of what SaaSFlow offers AI agents, see saasflow.com/agents.
REST API
HTTPS, JSON, three auth modes. The Explorer runs against this.
CLI
`saasflow` — terminal access for scripts, CI, and ad-hoc queries.
MCP server
Hosted at `api.saasflow.com/mcp`. Expose SaaSFlow as tools to Claude and other MCP clients.
API reference
Every endpoint with parameters, responses, code samples, and a built-in try-it playground.
Pick your path
| If you want to… | Use |
|---|---|
| Embed SaaSFlow data in your own product | REST API |
| Run one-off queries from your terminal | CLI |
| Let an LLM ask questions about your finances | MCP server |
| Try requests interactively before writing code | API reference |
| Build a third-party app users can install | OAuth for apps |
Conventions
- Base URL:
https://api.saasflow.com - Format: JSON in and out
- Authentication: session cookie, API key, or OAuth bearer — see Authentication
- Resource scoping: everything (except
/companiesitself) is under/companies/{companyId}/…
The OpenAPI spec is also available as a JSON document, served from these docs at
/openapi.json or fetched live and unauthenticated from
https://api.saasflow.com/openapi.json.
Each operation lists the permission an API key needs (x-saasflow-permissions) and the
OAuth scope a third-party app must hold. An RFC 9727 API catalog
and an MCP server card point agents and tooling at the same places.