Lead ingestion

Nolo & 4All campaigns – receive and store lead data in JSON

API base:

How leads are received

Nolo (nested JSON, campaign in URL):

  • Endpoint: POST /api/v1/leads/{campaign_id}
  • Header: Authorization: Bearer <NOLO_BEARER_TOKEN>

Legacy / 4All (flat JSON, campaign in body):

  • Endpoint: POST /api/leads
  • Header: X-API-Key: <FOURALL_API_KEY>

Success: 200 OK with JSON data.lead, data.user, data.profile (matches production GeniusLaw).

Example body:

{
  "user": {
    "first_name": "Anish",
    "last_name": "Test",
    "email": "anish.test@example.com",
    "phone": "5559876543"
  },
  "lead": {
    "description": "API connectivity test"
  },
  "profile": {
    "state": "CA",
    "address": "",
    "county": "Los Angeles",
    "city": "Los Angeles"
  }
}

Received leads

Loading…

Test API keys

Check if keys from .env are loaded and verify a key without sending a lead.

Nolo key in .env: — 4All key in .env: —

Test submission

Send a test lead the same way Nolo does. Campaign ID goes in the URL (e.g. /api/v1/leads/1).