Advanced Users / Developers

Get an API key from Settings → Integrations or API. Send requests to the API base URL (e.g. /api/v1/leads) with the key in a header (e.g. X-API-Key or Authorization). Use GET to list/read, POST to create, PATCH to update. See API docs or Settings for endpoints and schema.

Check Settings → Integrations or the Help/Developers section for API base URL and a short reference. Full docs may be linked from there or from the main Help Center.

It’s your LeadLock domain + path (e.g. https://yourapp.com/api/v1). Exact path is in Settings → API or Integrations. Use it for all API calls (e.g. GET /leads, POST /leads).

Include your API key in every request. Common pattern: header X-API-Key: your-key or Authorization: Bearer your-key. Create or copy the key from the CRM Settings. Never expose the key in frontend code.

Option 1 – Webhook: POST to the inbound webhook URL with JSON (name, email, phone, etc.). Option 2 – API: POST to the leads endpoint (e.g. /api/v1/leads) with the same fields and your API key. Both create a lead in the CRM.

1. Locate API settings: Settings then Integrations or API. 2. Generate or copy an API key if your plan supports it. 3. Use your app or Postman: set the request URL to your LeadLock base URL plus the leads path (e.g. /api/leads). 4. Add the API key in a header (e.g. X-API-Key or Authorization: Bearer your-key). 5. Send a POST with JSON body: name (required), email, phone, company, source, etc. 6. Confirm the response is success and the lead appears in Leads.

Webhooks, Make.com, Integrations, Troubleshooting.