Integrate directly with the Lead Launcher Hub API.

1. Overview

The Lead Launcher Hub API lets authorised partners submit buyer profiles directly into our platform. Every submission is qualified using our behavioral qualification engine, assigned a plain-language priority tier, and routed to the right team automatically — no dashboard login required on your end.

Your integration receives a priority tier and a ready-to-use coaching note for the sales team. It does not receive raw scores, weightings, or any detail of how the qualification engine reaches its result — that logic stays internal, the same way it does everywhere else in our product.

2. Getting Access

API access is issued per partner and tied to your account plan. There's no public self-serve signup — each integration is set up directly with our team so we can configure your track, key, and call limits correctly from day one.

• Tell us about your use case (CRM export, partner portal, direct outreach tooling, etc.)
• We issue your token, agent key, and sandbox credentials
• We walk you through the field mapping specific to your integration

3. Authentication

Every request must include your unique API token. Pass it as a URL query parameter or as an HTTP header — both are supported.

Option A — URL Query Parameter

POST /api/leads/external?token=llh_live_YOUR_TOKEN

Option B — HTTP Header

POST /api/leads/external
x-token: llh_live_YOUR_TOKEN

Your token is issued to you separately during onboarding. Keep it confidential — never expose it in client-side code or public repositories.

4. Endpoint

5. Request Payload

Send a JSON body with the fields below. Required fields are marked with *.

Track Selection

track determines which property category and qualification model is used: A = Residential, B = Plot/Land, C = Institutional.

The answers Object

answers is an object with integer keys (question index) and integer values (the buyer's selected option). The exact question wording and option mapping for each track is specific to your integration and is provided directly during onboarding — it isn't published in this guide.

6. Example Request

Illustrative shape only — your onboarding materials include the live field mapping for your track.

POST /api/leads/external?token=llh_live_YOUR_TOKEN
Content-Type: application/json

{
  "name":     "Jane Doe",
  "phone":    "9876543210",
  "email":    "jane@example.com",
  "track":    "A",
  "answers":  { "0": 3, "1": 2, "2": 1, "3": 3, "4": 4 },
  "bonusAns": 4,
  "key":      "YOUR_AGENT_KEY",
  "vertical": "MY712",
  "source":   "CRM Export"
}

7. Response

A successful submission returns HTTP 201 with the qualification result.

HTTP/1.1 201 Created
Content-Type: application/json

{
  "success":    true,
  "message":    "Lead saved successfully",
  "data": {
    "lead_id":    153,
    "vertical":   "realestate",
    "created_at": "2026-08-11T10:30:00.000Z",
    "persona":    "Residential",
    "temperature":"Hot Lead",
    "tier":       "L2",
    "agent_note": "Contact within 2 hrs. Lead with the best available units and possession dates.",
    "alert_msg":  "New qualified lead received — see CRM for details."
  }
}

We don't return raw numeric scores or internal thresholds through the API — only the qualitative tier and note, consistent with how AiPIQS™ works everywhere else.

8. Error Reference

9. Rate Limits & Usage

Your token's monthly call volume is tied to your plan. Once you reach your limit, requests return HTTP 429 until it resets. Contact us anytime to check your current usage or discuss a plan upgrade.

10. Support

For integration support, token renewals, or plan upgrades, reach out to our team:

Please include your token prefix (first 12 characters only) and the lead_id of any failed submission when reporting an issue.