Overview & Quickstart

The Legenex API lets you post leads into the platform, receive real-time acceptance decisions, and read back delivery, feedback, and reporting data.

How posting works

You send a lead as a JSON payload to a single ingestion endpoint. Legenex authenticates the request, validates and normalises the fields, runs enrichment (phone / email verification), routes the lead to the right buyer or delivery bucket, and returns a structured decision envelope describing the outcome.

Every response follows the same layered envelope so you can key your own automation off a small, stable set of fields regardless of outcome. See the Response Reference for the full schema.

Base URL & environments

Environment	Base URL
Production	`https://api.legenex.com`
Docs	`https://docs.legenex.com`

All endpoints are served over HTTPS only. Requests over plain HTTP are rejected.

Quickstart: post your first lead

Send a single lead with your supplier API key in the X-API-KEY header:

POSThttps://api.legenex.com/functions/leads

bash

curl -X POST https://api.legenex.com/functions/leads \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: lgnx_int_xxxxxxxxxxxx" \
  -d '{
    "first_name": "Nick",
    "last_name": "Allen",
    "email": "nick@example.com",
    "mobile": "+15125550123",
    "zip": "78701",
    "accident_state": "TX",
    "trustedform_url": "https://cert.trustedform.com/abc123",
    "sid": "LEADFLOW",
    "s1": "clickid_9f2a"
  }'

A successful, sold lead returns:

json

{
  "ok": true,
  "trace_id": "trc_7c1f9a",
  "acceptance": "accepted",
  "lead_id": 84213,
  "lead_status": "sold",
  "sold": true,
  "revenue": 42.5,
  "currency": "USD",
  "code": "SOLD",
  "message": "Lead accepted and sold.",
  "Response": "Success"
}

Next steps

Head to Authentication to manage keys, Post a Lead for the full request contract, and the Field Dictionary for every accepted field.