CheckFlow API
CheckFlow can be reached from code in three ways. They share the same API keys, which Administrators create on the API & Integrations tab of Team Management.
| Use it for | Plans | |
|---|---|---|
| CheckFlow API v3 | Integrations you write: syncing checklists and tasks with other systems, building templates in code, managing Data Sets, schedules and webhooks. | Every plan |
| MCP Server | Letting an AI assistant such as Claude work in your workspace in plain language. | Every plan |
| Legacy API (v1 and v2) | Existing integrations, including the Zapier app. | Every plan |
Which to Choose
- Writing a new integration? Use the v3 API. Start with Getting Started.
- Want to ask an assistant to do the work? Connect the MCP server — see Connecting a Client.
- Maintaining an integration built on the legacy API? It keeps working. When you are ready, Migrating from v1 and v2 maps every legacy endpoint to its v3 equivalent.
- Would rather not write code? The Zapier app connects CheckFlow to several thousand other services without any.
Related Pages
- CheckFlow API v3 — base URLs, conventions and every endpoint group.
- Authentication — creating keys and choosing who each one acts as.
- MCP Server — connecting an AI assistant.
- Web Hooks — being told when something happens, instead of polling for it.