ClonifyDevelopersOpen panel

Getting started

  • Authentication
  • Errors
  • Pagination
  • Rate limits
  • Webhooks
  • For AI agents
  • MCP server

API reference

  • Student learning activity6
  • External API deliveries6
  • Chat with the clone1
  • Contacts & tags5
  • Academy access4
  • Conversations4
  • Product catalogue11
  • External sales2
  • Knowledge12
  • Multimedia4
  • Clones (versions in the API)3
  • Meetings & bookings3
  • Webinars6
  • Account & usage1
Clonify

Clonify for developers

Clonify API

Connect your own system (your CRM, your app, Make…) to your Clonify account: read your conversations, contacts and transcripts, and build from the outside. Add content to your Knowledge and create products, FAQs and clones. The API speaks JSON over HTTPS and follows the same rules as the panel: your plan quotas and feature locks are enforced automatically.

Base URLhttps://www.clonify.com/api/v1
01

Authentication

To connect a chat, choose Chat only. Create your key in the panel: Settings → API keys and webhooks. You can have several (one per connected system), each read-only, read & write, or full (with delete). The key is shown ONCE: store it like a password. Send it on every request in the Authorization header.

bash
curl "https://www.clonify.com/api/v1/conversations?limit=5" \
  -H "Authorization: Bearer clk_live_…"

For a chat integration, choose Chat only (chat). It only authorizes POST /api/v1/chat and uses your plan’s responses. Management permissions are separate: read allows data exports, including knowledge content; write includes read and also allows chat; delete includes the preceding management permissions. Missing permissions return 403 insufficient_scope.

02

Errors

Every error shares the same JSON shape, with a stable code in 'type' (for your code) and a readable message in 'message' (for humans). Status codes: 400 invalid request, 401 missing or revoked key, 403 no permission / feature outside your plan / quota exhausted, 404 not found in your account, 409 conflict (e.g. transcript not ready yet), 429 rate limited, 500 our fault.

json
{
  "error": {
    "type": "invalid_updated_since",
    "message": "'updated_since' no es una fecha válida (usa ISO 8601)."
  }
}
03

Pagination

Large lists are traversed by cursor: request with ?limit= and chain ?starting_after=<last id> while has_more is true. The cursor is stable by id: you can walk the whole history without missing or duplicating items. Bounded catalogues (tags, clones, products) come whole in one response.

json
{
  "object": "list",
  "data": [ … ],
  "has_more": true,
  "next_starting_after": 95
}
04

Rate limits

Each account has a per-minute request budget by plan: 60 (Starter), 120 (Pro) or 300 (Scale), shared across all its keys. Every response includes the X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers. When exceeded you get 429 with Retry-After (wait and retry with backoff). The limit stops runaway scripts, not real use: at 120/min you can export 12,000 conversations per minute.

Note: this is different from your plan quotas (clone responses, knowledge words). Check those via GET /api/v1/usage — they are enforced exactly like in the panel.

05

Webhooks

Besides reading on demand, Clonify can notify you in real time: set your URL in Settings → API keys and webhooks and you'll receive lead.created (new contact captured by the clone), conversation.ended (real conversation finished after 10 minutes without messages, with its messages; panel tests are never sent) and purchase.created (every recorded purchase, with the buyer's email, the product and the amount). Each event is switched on separately. Every delivery is signed with HMAC-SHA256 in the signature header using your whsec_… secret. Verify the signature before processing.

06

For AI agents

If an AI writes your integration (ChatGPT, Claude…), it has two shortcuts built for machines, not for human eyes. And if you'd rather not code at all: Clonify also exposes an MCP server with 100+ tools. Connect it from Settings → Connect your AI.

openapi.jsonThe full API specification in OpenAPI format: the contract an AI or an SDK generator consumes directly. For humans, the readable reference is this very site.llms.txtThis documentation's index in plain text (llms.txt pattern): hand it to your AI agent as the entry point.

Connect an AI without writing code: the MCP server

07

API reference

  • Student learning activity6 endpoints
  • External API deliveries6 endpoints
  • Chat with the clone1 endpoints
  • Contacts & tags5 endpoints
  • Academy access4 endpoints
  • Conversations4 endpoints
  • Product catalogue11 endpoints
  • External sales2 endpoints
  • Knowledge12 endpoints
  • Multimedia4 endpoints
  • Clones (versions in the API)3 endpoints
  • Meetings & bookings3 endpoints
  • Webinars6 endpoints
  • Account & usage1 endpoints