Supply Consent Evidence for External Leads

Submit Leadping Consent or TrustedForm evidence in a supported intake field and recover pending or invalid certificates.

Every external lead needs its own consent evidence: an issued Leadping Consent certificate ID or a TrustedForm certificate URL. Your account’s Profile consent is separate from the evidence for a lead.

A screenshot, consent timestamp, landing-page URL, or arbitrary internal ID does not replace a supported certificate. Capture evidence for the actual submission and preserve it through every handoff.

Add the certificate field

Endpoint	Supported evidence field
POST /leads	metadata.leadpingConsentCertificateId or metadata.trustedFormUrl
POST /leads/intake	trustedFormUrl only

The flat request model does not map Leadping Consent IDs. For that evidence, use the structured Leadping Consent example. Supply one evidence type: if both are present, Leadping Consent is checked first, with no fallback to TrustedForm on failure.

The following examples use TrustedForm. Replace the placeholder with a real certificate for the submitted contact.

Structured request

{
  "metadata": {
    "trustedFormUrl": "https://cert.trustedform.com/example"
  },
  "contact": {
    "firstName": "Jordan",
    "phone": {
      "number": "[phone]"
    }
  },
  "customer": {},
  "tagIds": [],
  "tagNames": []
}

Flat request

{
  "firstName": "Jordan",
  "phone": "[phone]",
  "trustedFormUrl": "https://cert.trustedform.com/example"
}

Leadping does not provide a GET or query-string intake endpoint.

Understand the result

For TrustedForm, Leadping checks certificate URL availability before outreach. The URL must identify one certificate on https://cert.trustedform.com without credentials, a query, a fragment, or a custom port. An HTTP 200 OK response passes this check; 404 Not Found marks the certificate invalid. Temporary service failures keep the lead in quarantine and retry after five minutes.

The TrustedForm availability check does not inspect certificate contents or verify consent language or recipient matching. Leadping Consent validation instead requires an accepted, complete recording and a recipient matching the submitted contact. A certificate reused for a different lead in the same organization is rejected.

Certificate handling has these customer-visible states:

Result	Meaning	Next action
400 Bad Request for missing supported evidence	Intake did not create the lead	Correct the mapping before sending again
201 Created, lead still processing	The record exists; certificate availability and lead processing are not finished	Keep the lead ID and inspect its processing status
Ready	Lead processing completed	Check the intended workflow separately
Quarantined after a temporary certificate-check failure	Outreach is paused and the availability check will retry	Keep the existing lead; read its processing reason
Invalid	The lead did not pass validation, including a certificate 404 response	Read the processing reason and correct the source of the problem

An accepted request is not evidence that the certificate matches the person, sender, or intended outreach. Your team must be able to explain that relationship from the original submission and its consent records.

Leadping Consent issuance and recovery

The Portal captures account consent automatically; follow Profile recovery if onboarding is blocked. The sequence below explains that flow and the distinction between pending capture and ready evidence. It is not a way to create a certificate by posting an invented UUID.

Request or state	Expected behavior	Recovery
Portal opens /setup/personal	Browser starts POST https://consent.leadping.ai/api/consent/domains/leadping/sessions with the current page URL and disclosure	If initialization fails, reload the Profile page; its SMS checkbox stays unavailable until capture starts
Customer accepts and selects Next	Portal calls PUT /users/personal; the capture SDK uploads the recording and seals the submission	Correct personal validation errors first; autosave alone does not verify consent
POST /api/consent/certificates with the capture reference returns 202 Accepted	Recording is saved; certificate issuance is pending. Response contains the same certificateId as the capture’s sessionId	Repeat issuance with the same { sessionId, uploadToken }; do not seal another recording. Portal handles this automatically with a delay of 1, 2, 4, then at most 5 seconds
Same issuance request returns 200 OK	Certificate has been issued	Portal sends PUT /users/compliance with compliance.consentCertificates and source Personal; the server verifies it before the Portal advances to Organization
Issuance fails or returns an unexpected certificate ID	Profile cannot advance	Follow the displayed reload/retry instruction; contact support if it repeats
Authorized certificate verification returns 202	Certificate still processing; the validator reports a pending-certificate conflict internally	Keep the same certificate and wait for issuance. This internal result is not a promise that every calling API exposes HTTP 409
External lead is posted before its certificate is issued	Intake may return 201, but the background worker currently marks pending evidence Invalid	Keep the lead ID, wait for issuance, and contact support to recover processing of that record. Reposting the same deduplication key returns the existing record; it does not restart validation
Certificate verification is temporarily unavailable	External lead processing pauses in Quarantined and retries	Keep the record and inspect its processing reason; do not create a replacement
Certificate is missing, incomplete, unaccepted, mismatched, or already used by another lead	Validation fails	Correct capture or mapping for the original submission; never borrow another person’s or your account’s certificate

For an external Leadping Consent form, use its registered domain and disclosure; the leadping account domain above is for the Portal’s own form. Obtain an issued certificate from that integration before posting the lead. Browser capture tokens are write-only and are not source API keys or credentials for reading evidence. Keep source and certificate-read credentials on the server.

For account Profile verification, Leadping also checks the Portal origin, /setup/personal path, registered disclosure, and fresh evidence (within one hour, with at most one minute of future clock tolerance). If the saved contact changes or evidence becomes stale, return to Profile and capture fresh consent.

Trace a certificate through the integration

1. For the TrustedForm path, install TrustedForm on the actual form where the person submits their information, following ActiveProspect’s setup guide.
2. Complete a controlled submission and confirm that it produces a certificate URL.
3. Inspect the form-to-backend handoff. Confirm that the URL travels with the same contact and upstream record ID.
4. Check each CRM, partner, or middleware mapping. A generic URL field can accidentally contain the landing-page address instead of the certificate.
5. Inspect the final Leadping record and compare its certificate with the original submission.

If the form does not produce a certificate, fix capture at the form. If the certificate exists there but is absent from Leadping, locate the first handoff that drops or replaces it. Do not create a new certificate for an old submission or reuse one from another person.

Integration requirements

• Capture a unique certificate for each lead at the opt-in form.
• Carry the complete TrustedForm URL or issued Leadping Consent ID through every form, webhook, CRM, and posting step.
• Do not substitute a landing page, screenshot, consent timestamp, capture reference, or arbitrary internal ID.
• Keep retries associated with the same lead and certificate.
• Confirm a production-path test reaches Ready in Leadping.

TrustedForm records the opt-in event. It does not override an opt-out, correct inadequate consent language, or make an otherwise unlawful contact permissible.

Troubleshoot validation

Result	Cause	Correction
Intake returns 400	Supported evidence field is missing	Restore the mapping; for Leadping Consent use structured POST /leads
Lead becomes Invalid	URL is malformed or incomplete	Submit the complete certificate URL
Lead becomes Invalid	A landing page or unrelated URL was supplied	Use the certificate issued for the original submission
Lead becomes Invalid	Certificate availability check returned HTTP 404 Not Found	Check certificate capture and availability
Wrong certificate appears	A handoff reused or replaced the value	Preserve the certificate associated with that lead

Fix the underlying integration before sending more traffic.

Retention

The following retention guidance applies to TrustedForm.

Storing a URL in Leadping is not the same as retaining the certificate with ActiveProspect. Assign an owner for retention and verify that the retained certificate can be retrieved from the responsible account.

Expiration depends on certificate and account conditions. Use ActiveProspect’s expiration and retention guidance to configure retention rather than assuming one default window covers every lead. Keep the related form disclosure, submission timestamp, and source record as well as the certificate.

Configure the source

Create the intake identity and obtain its source key.

Send leads

Build requests and handle processing results.