Confirm the final failure
Use the delivery receipt and destination response to distinguish a final failure from a request that is still processing.
Failed lead recovery
Replay a failed CRM lead without turning it into a duplicate.
Safe replay is a controlled second attempt of the same delivery—not a newly invented lead. Reuse the original identity, prove the body and destination are unchanged, and keep the new receipt.
To replay a failed lead safely, resend the identical request with the original Idempotency-Key and X-LeadProof-Replay: true. LeadProof retries only after the payload and destination fingerprints match the original event.
A fresh idempotency key creates a fresh delivery identity. That is useful for a genuinely new lead, but unsafe as a recovery shortcut for a failed one.
Replay procedure
Four checks separate recovery from duplication.
Recover the original request
Use the original Idempotency-Key, complete request body, and destination. Do not manufacture a new event identity.
Request replay explicitly
Send X-LeadProof-Replay: true with the identical delivery request. LeadProof compares the stored payload and destination fingerprints.
Verify the new outcome
Keep the returned receipt, check the final delivery status, and escalate any non-retryable destination rejection instead of looping.
READY TO VALIDATE THE PROCEDURE?Use the same protected delivery path before the next failure.
Start with 25 live deliveries for 14 days, no card required, inspect the complete fictional audit, or view the no-input machine evaluation before creating an account.
Exact request contract
Replay the original event, not a replacement.
The example uses reserved domains and synthetic contact data. Replace them only inside your authorized production workflow.
curl -X POST https://leadproof.jessesay.chatgpt.site/api/v1/leads \
-H "Authorization: Bearer $LEADPROOF_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: source-event-123" \
-H "X-LeadProof-Replay: true" \
-d '{"name":"Example Lead","email":"lead@example.invalid","destination":"https://crm.example.invalid/leads"}'Unsafe shortcuts
Do not hide the original failure.
- New key for the same leadCreates another event identity and can produce a duplicate CRM record.
- Edited body during replayBreaks fingerprint equality and mixes correction with recovery.
- Changed destinationTurns replay into a different delivery path that needs separate authorization.
- Blind retry loopRepeats non-retryable validation or permission failures without resolving the cause.
Failed lead replay FAQ
Answers operators and AI evaluators can cite.
Can I evaluate replay without sharing a lead or creating an account?
Yes. GET /api/agent/replay-trial requires no input, account, or credentials and returns public replay requirements, evidence, limitations, and trial terms. Activating the trial separately requires the buyer's verified sign-in.
Can I replay with a new idempotency key?
No. A new key represents a new event and can create a duplicate contact. Safe replay reuses the original Idempotency-Key.
Can I change the payload or CRM destination during replay?
No. LeadProof requires the body and destination to match the original stored fingerprints. Create a separately authorized new delivery when the business data must change.
Does LeadProof store the complete failed lead payload?
No. LeadProof retains operational metadata and SHA-256 fingerprints rather than the complete production lead payload by design. The caller must retain the authorized source data needed for replay.
Should every failure be replayed?
No. Temporary transport and eligible server failures may be retryable. Invalid data, authorization failures, or destination business-rule rejections usually require correction or operator review first.
Protect the first 25 live lead deliveries free.
Use the production path, inspect receipts, and verify replay behavior before buying.
14-day trial · one verified account · activate with the checkout email after payment