Require TrustedForm for External Leads

Every external lead sent to Leadping requires its own TrustedForm certificate URL.

No certificate, no lead. Leadping rejects an external intake request when the TrustedForm URL is missing.

Add the certificate field

Endpoint	Required field
`POST /leads`	`metadata.trustedFormUrl`
`POST /leads/intake`	`trustedFormUrl`

Structured request

{
  "metadata": {
    "trustedFormUrl": "https://cert.trustedform.com/example"
  },
  "contact": {
    "firstName": "Jordan",
    "phone": {
      "number": "+15555550123"
    }
  },
  "customer": {}
}

Flat request

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

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

What Leadping validates

Lead creation and certificate validation happen in two stages.

During intake

Leadping confirms that the TrustedForm field is present. A missing value returns 400 Bad Request, and no lead is created.

After creation

A successfully created lead begins in Verifying. Leadping checks that the certificate URL:

is an absolute HTTP or HTTPS URL;
uses trustedform.com or one of its subdomains; and
returns 200 OK when Leadping requests it.

If those checks pass, Leadping records trustedFormCheckedAt and continues processing the lead toward Ready. If they fail, the lead moves to Invalid and its processing-status reason describes the failure.

201 Created means the lead passed immediate intake validation. It does not mean TrustedForm verification has finished. Check the lead’s processing status before treating it as ready.

Integration requirements

Capture a unique certificate for each lead at the opt-in form.
Carry the complete URL through every form, webhook, CRM, and posting step.
Do not substitute a landing page, screenshot, consent timestamp, or 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`	Certificate field is missing	Restore the field mapping before retrying
Lead becomes Invalid	URL is malformed or incomplete	Submit the complete certificate URL
Lead becomes Invalid	URL is not hosted on `trustedform.com`	Submit the URL issued by TrustedForm
Lead becomes Invalid	Certificate URL cannot be reached successfully	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

TrustedForm certificates can expire unless retention is extended. Assign responsibility for retention before production traffic begins, and preserve certificates and related source records for applicable legal, contractual, carrier, audit, and dispute requirements.

Configure the source

Create the intake identity and obtain its source key.

Send leads

Build requests and handle processing results.

Start Here

Build Your Workflow

Prepare for Production

Build with Leadping

Security & Trust

Policies & Legal

Require TrustedForm for External Leads

Add the certificate field

Structured request

Flat request

What Leadping validates

During intake

After creation

Integration requirements

Troubleshoot validation

Retention

Configure the source

Send leads

​Add the certificate field

​Structured request

​Flat request

​What Leadping validates

​During intake

​After creation

​Integration requirements

​Troubleshoot validation

​Retention

Configure the source

Send leads

Add the certificate field

Structured request

Flat request

What Leadping validates

During intake

After creation

Integration requirements

Troubleshoot validation

Retention