Developers

API & webhooks

Send leads into LeadForGrow from any website, landing page builder or app, and start automation workflows from your own systems. All requests are JSON over HTTPS.

Secret-based authentication Constant-time secret checks Base URL https://www.leadforgrow.com

Submit a form

POST /api/forms/submit

Creates a lead from a LeadForGrow form — use it when you build your own form instead of the embed.

Authentication

The form’s public token in the body. Find it in Forms → your form → Publish & embed.

Body

token: string; Required. The form token.
name: string; Lead name.
email: string; Email or phone is required.
phone: string; With country code, e.g. 919876543210.
…any field: string; Other form fields are saved on the lead.

Errors

400 Missing token
404 Invalid or inactive form
429 More than 5 submissions a minute from one address

curl -X POST https://www.leadforgrow.com/api/forms/submit \
  -H "Content-Type: application/json" \
  -d '{
    "token": "YOUR_FORM_TOKEN",
    "name": "Jane Doe",
    "email": "jane@example.com",
    "phone": "919876543210",
    "message": "Need a quote"
  }'

Trigger a workflow

POST /api/automation/webhooks/{sequenceId}/{secret}

Starts a sequence whose trigger is “Webhook”. Creates the lead if needed, or runs for an existing lead.

Authentication

Copy the full URL from the sequence’s Workflow settings. Instead of the secret in the URL you may send it as an x-api-key header, or sign the raw body with HMAC-SHA256 in X-Webhook-Signature (sha256=<hex>).

Body

leadId: string; Run for this existing lead. If omitted, a lead is created from the fields below.
name: string; Also accepts full_name.
email: string
phone: string; Also accepts mobile.
…any field: any; The whole body is stored with the lead and is available to the workflow.

Errors

400 Body is not valid JSON
401 Secret, key or signature does not match
404 Workflow not found, or its trigger is not Webhook
422 No lead could be created (no email or phone)

curl -X POST https://www.leadforgrow.com/api/automation/webhooks/SEQUENCE_ID/SECRET \
  -H "Content-Type: application/json" \
  -d '{ "name": "Ravi", "phone": "919812345678", "plan": "gold" }'

Errors & limits

Every response is JSON with success true or false; failures include an error message.
A lead needs an email address or a phone number.
Leads count towards your plan’s monthly lead limit; requests over the limit are refused with a clear message.
Keep secrets on your server. Anyone with a workflow URL can start that workflow, so treat it like a password.

Need something these endpoints don’t cover? Tell us what you’re building.