LPLeadProofStart free

LeadProof API v1

Deliver a verified lead in minutes.

Send structured lead data to LeadProof. We normalize it, deliver it to your HTTPS destination, retry temporary failures, and return proof of the final state.

Quickstart

The public sandbox performs the complete normalization and receipt flow without contacting an external CRM. No API key is required.

Run the fixed synthetic sample in your browser →

curl https://leadproof.jessesay.chatgpt.site/api/v1/sandbox \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Alex Morgan",
    "email": " ALEX@ACME.IO ",
    "phone": "(555) 013-4821",
    "source": "web_form"
  }'

Verification receipt

{
  "status": "delivered",
  "mode": "sandbox",
  "normalized": {
    "email": "alex@acme.io",
    "phone": "+15550134821"
  },
  "delivery": {
    "attempts": 1,
    "verified": true
  },
  "receipt": {
    "id": "rcp_test_...",
    "created_at": "2026-07-18T...Z"
  }
}

POST /v1/sandbox

Use the sandbox for integration development, automated tests, or evaluating LeadProof. It never forwards personal data to an external destination.

POST /v1/leads

The production endpoint requires an active API key, a public HTTPS destination, and an optional Idempotency-Key. It retries network errors, 429 responses, and 5xx responses up to three total attempts.

Privacy by design

LeadProof stores delivery metadata and a SHA-256 payload fingerprint—not the full lead payload. The destination receives the normalized record.

Ready for production?

Builder includes 2,500 lead events, secure activation, a private operations dashboard, and fingerprint-verified replay.

Protect 25 live leads free →Already proven? Start Builder · $49/monthNo-card trial first · real production API · secure Stripe checkout for Builder · activate with the checkout email after payment

Error behavior

401Missing or invalid API key
422Invalid lead or unsafe destination
502Destination was not verified after retries