Random retry keys
Generating a fresh UUID for each attempt makes every resend look like a new lead.
Idempotency keys for lead delivery
Choose an idempotency key that survives every lead-delivery retry.
Prevent duplicate CRM contacts by deriving one stable key from the original form, call, booking, conversation, or source event.
A successful automation run is not proof of delivery.
Idempotency works only when every retry of one logical event uses the same key. A timestamp, random UUID generated inside the retry branch, or destination attempt number produces a new identity and defeats duplicate protection.
Durable source event ID -> Idempotency-Key -> one LeadProof receipt identityMutable field keys
Using email or phone can merge distinct submissions or change after normalization.
Unbounded identifiers
Large or sensitive values make logs harder to manage and can expose unnecessary information.
Implementation
Put LeadProof in the delivery path.
Keep the tools that create and process the lead. Standardize only the fragile handoff between them.
Open sandbox instructions →- Select the durable submission, call, booking, conversation, or opportunity event ID at capture time.
- Keep the key opaque, non-sensitive, and 120 characters or fewer.
- Send the same value in Idempotency-Key for the original delivery and every retry.
- Persist the returned receipt ID beside the source event for later reconciliation.
POST
https://leadproof.jessesay.chatgpt.site/api/v1/leadsAuthorization: Bearer lp_live_your_key
Idempotency-Key: stable-source-lead-id
Content-Type: application/json
{
"destination": "https://your-crm.example/webhook",
"name": "Alex Morgan",
"email": "alex@example.com",
"source": "idempotency"
}Questions
What teams ask before adding LeadProof.
Should I use the lead email as the key?
No. Prefer a non-sensitive source event ID because one person can submit more than once and contact data can change.
Can I use a timestamp?
Only if it was assigned once to the original source event and reused exactly. A new timestamp per retry defeats idempotency.
What does LeadProof return for a completed duplicate request?
It returns the stored delivery state and receipt instead of forwarding the same event again.
See the gaps in your real workflow.
Get an explainable risk score, prioritized fixes, and the right LeadProof plan.