Developers

Connect Claude (or any tool) to your processes. Same permissions, same plan limits, same validation — just a different front door.

Connect Claude (MCP)

Recommended

The fastest way to let Claude Desktop or Claude Code read, create, and publish your processes — drop a single line into your Claude config.

Open

REST API reference

v1

Full HTTP reference — authentication, endpoints, rate limits, errors, examples. Includes a one-click "Copy as Markdown" button so you can paste it into any LLM conversation.

Open

OpenAPI spec

JSON

Machine-readable schema of every endpoint. Drop into Postman, Insomnia, Stoplight, or any OpenAPI-aware client.

Open

Zapier integration

Live

Trigger on process creation, push new SOPs in from Google Docs / Airtable / Typeform. Same underlying API key system.

Open

What you get

  • Personal API keys — any signed-in user can mint one at /account/api-keys
  • Org keys with role inheritance — member keys are scoped to member permissions
  • Member-request approval flow — owners/admins gate key creation for members
  • Permission scopes — processes:read, processes:write, processes:delete
  • Image uploads via POST /uploads — attach screenshots without needing your own image host
  • Rate limits per plan — Free included, 200 requests/day on the free tier
  • Same validation engine — URL checks, plan limits, version snapshots, all applied to API calls

Using Claude? Skip the boilerplate.

Paste /developers/api.md into a Claude conversation along with your API key. Claude will parse the reference and translate natural-language requests — "create a process called X", "publish the one about Y" — into the right HTTP calls. 

curl https://www.whatstheprocessfor.com/developers/api.md

Mint your first key

Personal keys live under your account; org keys live under your organization. Both are managed from the API keys page.

Manage API keys