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.
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 a pilot 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.
LeadProof stores delivery metadata and a SHA-256 payload fingerprint—not the full lead payload. The destination receives the normalized record.
Error behavior
| 401 | Missing or invalid API key |
| 422 | Invalid lead or unsafe destination |
| 502 | Destination was not verified after retries |