The Manifestly API
Manifestly has a public REST API for teams who want to drive it from their own systems rather than by hand. It sits alongside three other integration routes, and which you want depends on how much control you need.
What the API can do
- List and create workflows
- Create runs, and read their state
- Complete steps and set the data collected on them
- Read and manage your team members
The usual shape is another system creating a run when something happens in it, stamping the run with its own record id so the two can be matched later. See Associate a run with the ID of a record in a different system.
Which route to use
- Zapier, when the other system is a common SaaS tool. No code, and it covers most cases. See Does Manifestly integrate with other services?.
- Webhooks, when you want Manifestly to tell your system something happened. See Using Webhooks for Integrations and Automations.
- The API, when your system needs to ask Manifestly for things, or act on it, on its own schedule.
- MCP, when you want an AI assistant to work with your account conversationally. See Connecting AI Assistants to Manifestly.
Webhooks and the API are complements rather than alternatives: webhooks for us telling you, the API for you asking us.
Getting a key
API access is authenticated with a key you create in Settings → Integrations. See Managing API Keys.
One thing to know before you build: keys in the older 32-character format work with the REST API but are rejected by the MCP server. If you intend to use both, create a key in the current format.
Endpoints and support
We add endpoints as people need them, and will work with your development team on a use case that is not covered yet. If the API does not currently do what you need, tell us what you are building rather than working around it.
Video walkthrough
This video walks through the Manifestly API.