ChirplyChirply API documentation
One catalog of operations powers Chirply’s REST API, its built-in MCP server, its in-app assistant and its Zapier integration. Anything a person can do in the app, a program can do too — the same permissions, the same validation, the same effects.
Base URL https://app.chirply.io. Every endpoint is HTTPS-only and returns JSON. The live registry currently publishes 2,540 operations across 144 domains.
Your first call in five minutes
- Create an API key in the app under Developers. It starts with
chp_live_and is shown once. - Verify it with the whoami read — it answers with your workspace, your scopes and how many actions the key can reach.
- Run an action. Every operation is one POST to
/api/v1/actions/<name>.
curl https://app.chirply.io/api/v1 \
-H "Authorization: Bearer chp_live_…"
curl -X POST https://app.chirply.io/api/v1/actions/contacts.create \
-H "Authorization: Bearer chp_live_…" \
-H "Content-Type: application/json" \
-d '{"first_name":"Ada","last_name":"Lovelace","phone":"+15551234567"}'The quickstart walks each step with copy-paste curl, JavaScript and Python.
In this reference
- QuickstartYour first authenticated call in five minutes — curl, JavaScript or Python.
- AuthenticationAPI keys for your own scripts, and OAuth 2.0 for anything you distribute.
- ErrorsThe response envelope, the full status-code table, and how a client recovers.
- Rate limitsPer-credential budgets, the RateLimit headers, and how a polite client paces itself.
- WebhooksSigned event deliveries to your HTTPS endpoint, with retries and a delivery log.
- MCP & AI agentsPoint any MCP-capable assistant at your workspace — every operation is a tool.
- Actions reference2,540 operations across 144 domains, read live from the registry, with each one's input schema.
- REST resourcesConventional CRUD endpoints for contacts, deals and tasks, with pagination.
One registry, every surface
Chirply’s machine surfaces are thin adapters over a single capability registry. Each capability is defined once — its input schema, its permissions, its effect — and every surface exposes that same definition:
- REST —
POST /api/v1/actions/<name>, discovered atGET /api/v1/actionswith a JSON Schema per operation. - MCP —
https://app.chirply.io/api/mcpexposes every operation as a tool for AI agents, with the same bearer token. - Copilot — the in-app assistant runs the same operations on a signed-in user’s behalf, with human approval on consequential ones.
- Zapier — the Chirply Zapier app wraps the catalog for no-code automation.
Because none of the surfaces owns its own list, they cannot drift apart: the day a feature ships in the app, its operations are callable, discoverable and documented here.