> ## Documentation Index
> Fetch the complete documentation index at: https://leadping.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Consent

> How Leadping handles Verified, Unverified, and Quarantined consent.

## Consent states

| State | Meaning | Outreach |
| - | - | - |
| **Verified** | Leadping has validated supporting consent evidence. | Manual and automated, within its scope. |
| **Unverified** | You attest that you have consent, but Leadping has not independently verified it. | Manual outbound texts only. Leadping policy blocks automated outreach and calls. |
| **Quarantined** | Consent is missing, disputed, or has a material problem. | Outbound outreach is blocked pending resolution. |

Opt-outs, suppression, contact hours, and other sending restrictions still apply to every lead.

## Add consent

When adding or editing a lead, provide either:

* A **Leadping** or **TrustedForm** certificate URL.
* **Other:** check the box confirming that you have consent to text the lead. This gives the lead Unverified consent.

Leadping validates certificates before marking consent Verified. Leadping certificates are checked for accepted consent, a complete recording, and a matching recipient. TrustedForm certificates are checked for URL validity and availability; their contents and recipient are not independently checked.

To move from Unverified to Verified, add a supported certificate and wait for validation. Removing attestation without adding a certificate leaves consent Quarantined.

## API

Both `POST /leads` and `POST /leads/intake` accept these fields. Put them inside `metadata` for `POST /leads`, or at the top level for `/leads/intake`.

| Field | Value |
| - | - |
| `consentCertificateType` | `Leadping`, `TrustedForm`, or `Other` |
| `consentCertificateUrl` | Full certificate URL for Leadping or TrustedForm. Omit for Other. |
| `consentAttested` | `true` when attesting to Other consent. |

### Other consent example

```json theme={null}
{
  "firstName": "Jordan",
  "phone": "+15555550123",
  "idempotencyKey": "submission-4472",
  "consentCertificateType": "Other",
  "consentAttested": true
}
```

Other submissions need an idempotency key or `sellerLeadId`. Sources configured to require certificates still require them. Leadping sets `metadata.consentVerificationStatus` automatically.

See [Sending Leads](https://leadping.ai/docs/sending-leads-to-leadping.md) for certificate examples and authentication.

## CSV imports

Map email or phone, plus **Consent Certificate Url** or **Consent attested**. Use `true` to attest to Other consent without a certificate. Blank values, `false`, and `yes` do not count as attestation.

## Blocked outreach

Check the lead's **Consent verification** section and processing reason. Correct missing or invalid evidence, and resolve disputes or opt-outs before contacting the lead.

A lead must finish processing before outreach. **Ready** does not mean Verified: an Other lead can be Ready and still be limited to manual texts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.