Public API & MCP
Hashed API keys, a REST surface to list/trigger/read workflows, and an MCP endpoint that exposes your workflows as callable tools.
Pipory workflows are reachable from outside the editor two ways: a small REST API for scripting and integrations, and an MCP endpoint for MCP-compatible clients like Claude Code.
API keys
Open Account > API Keys to create a key. Keys are prefixed idl_, shown in full exactly once at creation time, and stored hashed - if you lose one, revoke it and create a new one rather than trying to recover it. Send it as a bearer token:
curl https://pipory.com/api/v1/workflows \
-H "Authorization: Bearer idl_..."REST endpoints
| Method | Path | What it does |
|---|---|---|
GET | /api/v1/workflows | Lists the key owner's workflows (id, name, enabled, timestamps). |
POST | /api/v1/workflows/[workflowId]/trigger | Triggers a run; the request body becomes the workflow's initialData, same as any other trigger. Returns the new execution id (waits briefly for the row to exist before responding). |
GET | /api/v1/executions/[executionId] | Reads an execution's status and output. Accepts either the execution's own id or the trigger call's event id, for the (rare) case the trigger response timed out before the execution row existed yet. |
Every endpoint requires the same Authorization: Bearer <key> header and scopes results to that key's owner - there is no cross-account access.
Workflows as MCP tools
/api/mcp is a stateless MCP server (the "Streamable HTTP" transport - JSON-RPC 2.0 over a single POST endpoint, authenticated with an API key) that exposes your webhook-enabled workflows as callable tools:
initialize- capability handshaketools/list- one tool per callable workflowtools/call- triggers the workflow and returns its output
Point an MCP-compatible client (Claude Code, for example) at /api/mcp with your API key and it can list and invoke your workflows as tools directly - the complement to the MCP Tool node, which lets a workflow call other MCP servers.
Related
- Node reference - the MCP Tool node, for calling MCP servers from inside a workflow.
- Executions - what an execution's status and output look like once you're polling
/api/v1/executions/[executionId]. - Credentials - how every other per-user secret in Pipory is stored; API keys follow the same per-user scoping.