Leads
Same contract as the MCP leads tool. Actions map to sub-routes.
POST
/api/agents/tools/leads/create · /get · /update · /qualify · /identifyAuth: Authorization: Bearer YOUR_API_KEY or x-api-key. Always send site_id.
Actions
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.
| Action | Route | Required body |
|---|---|---|
| create | POST /api/agents/tools/leads/create | site_id, name, email |
| list | POST /api/agents/tools/leads/get | site_id |
| update | POST /api/agents/tools/leads/update | site_id, lead_id |
| qualify | POST /api/agents/tools/leads/qualify | site_id, lead_id, status |
| identify | POST /api/agents/tools/leads/identify | site_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