Official quickstart clients
Go from API key to verified receipt with no package install.
Download one small client, keep the API key in an environment variable, and send every source event with a stable idempotency key. Both clients use only their language runtime and the official LeadProof production endpoint.
JavaScript client
Works in modern runtimes that provide the Fetch API. The API key property is non-enumerable, and the client does not persist or log it.
curl -O https://leadproof.jessesay.chatgpt.site/sdk/leadproof.mjs
import { LeadProofClient } from "./leadproof.mjs";
const client = new LeadProofClient(process.env.LEADPROOF_API_KEY);
const receipt = await client.deliver({
idempotencyKey: "form-submission-123",
destination: "https://your-crm.example/webhook",
name: "Sample Lead",
email: "lead@example.invalid",
source: "website_form"
});Python client
Uses only json and urllib from the Python 3 standard library. No package registry or dependency installation is required.
curl -O https://leadproof.jessesay.chatgpt.site/sdk/leadproof.py
import os
from leadproof import LeadProofClient
client = LeadProofClient(os.environ["LEADPROOF_API_KEY"])
receipt = client.deliver(
idempotency_key="form-submission-123",
destination="https://your-crm.example/webhook",
name="Sample Lead",
email="lead@example.invalid",
source="website_form",
)Safe defaults
| API origin | Hard-coded to the official LeadProof production endpoint so a custom base URL cannot receive the key. |
| Event identity | A non-empty Idempotency-Key of at most 120 characters is required for every delivery. |
| Destination | Must be HTTPS and cannot contain embedded credentials. The production API performs stricter public-network validation. |
| Errors | HTTP status and structured API details remain available, including trial upgrade paths when limits are reached. |
| Storage | Neither client writes the API key or complete lead payload to browser, file, or local application storage. |
Fingerprint-verified replay
After a final failure, call client.replay(...) with the original idempotency key, identical payload, and identical destination. The clients add X-LeadProof-Replay: true; the API verifies the stored fingerprints before retrying.
LeadProof intentionally stores operational metadata and SHA-256 fingerprints instead of the complete production lead body.
Activate one no-card API key for 25 live lead deliveries over 14 days, then upgrade only if the workflow proves its value.
Start the production trial →Already proven? Start Builder · $49/monthNo-card trial first · secure Stripe checkout for Builder · activate with the checkout email after payment