Skip to Content
The Makinari API repo now includes an MCP Server — connect your AI models directly. View on GitHub →

Leads

Same contract as the MCP leads tool. Actions map to sub-routes.

POST/api/agents/tools/leads/create · /get · /update · /qualify · /identify

Auth: Authorization: Bearer YOUR_API_KEY or x-api-key. Always send site_id.

Actions

Lead profile — interactive demo
Explore a sample lead profile to see the customer record represented by the lead endpoints below.
Sample workspace, not your live Site. This visual reference does not verify API calls or configure your integrations.
Open lead profile demo in a new tab ↗Scroll inside the demo to explore. If it does not load or you need more space, use the link above.
ActionRouteRequired body
createPOST /api/agents/tools/leads/createsite_id, name, email
listPOST /api/agents/tools/leads/getsite_id
updatePOST /api/agents/tools/leads/updatesite_id, lead_id
qualifyPOST /api/agents/tools/leads/qualifysite_id, lead_id, status
identifyPOST /api/agents/tools/leads/identifysite_id, visitor_id

status: new, contacted, qualified, converted, lost.

Optional on create/update: phone, position, company, notes, origin, segment_id, campaign_id, assignee_id, lead_score. List filters: search, limit (default 50), offset, sort_by, sort_order.

Create

curl -X POST "https://backend.makinari.com/api/agents/tools/leads/create" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "site_id": "YOUR_SITE_ID", "name": "Jane Smith", "email": "jane@example.com", "company": "Acme Corp", "status": "new" }'
{ "success": true, "lead": { "id": "...", "name": "Jane Smith", "email": "jane@example.com" } }

List

Typical errors: 400 missing email/name, 401 no key / no Origin, 403 missing write scope.

MCP schema: CRM tools.

Last updated on