Add-on: +1 credit per lookup
Set litigatorFilter: true on any lookup and we check the number against a TCPA litigator database refreshed daily. A match comes back with the litigator type and on-record name, and action is already set to "unsubscribe", so your suppression logic can key off one field.
| Number | The lookup says | Do this |
|---|---|---|
| (212) 555-0147 | Known TCPA litigator | Suppress |
| (305) 555-0123 | Mobile, not a known litigator | Send |
| (614) 555-0190 | Flagged, type "agitator" | Suppress |
| (512) 555-0168 | Landline, not a known litigator | Call list |
Fictional 555 numbers.
Each call or text that breaks the TCPA rules on autodialed or prerecorded calls can cost $500 in statutory damages, and up to three times that if the court finds it willful or knowing.
47 U.S.C. 227(b)(3) · law.cornell.edu
litigatorlitigator_type More than one call in 12 months that breaks the do-not-call rules lets the person sue for up to $500 per violation, or up to three times that if it was willful.
47 U.S.C. 227(c)(5) · law.cornell.edu
litigatordncComplainerResult Florida's Telephone Solicitation Act lets the called party recover actual damages or $500, whichever is greater, and up to three times that for willful violations. For texts, the person must first reply STOP and give the sender 15 days.
Fla. Stat. 501.059(10) · leg.state.fl.us
litigatorreason About 1.5% of the numbers we check come back flagged as TCPA litigators when the scrub is on. Litigators, plaintiffs and agitators all carry the same recommended action.
Source: CheckThatPhone lookup data
litigatorlitigator_type Teams that run it: real estate agents and investors, insurance lead buyers, call centers, collection agencies, SMS marketers and lead sellers.
Run every uploaded list through once, before it reaches your campaign tool: upload the CSV with the litigator scrub ticked, or call the API per number. The cheapest pattern at 2 credits per number, but it misses anyone added to the litigator data after the upload.
Call the API right before the first message or call to a number. Always current, and it catches recent additions to the litigator data, but it costs a lookup per send and adds a request to the send path.
A nightly job re-scrubs the active list and refreshes a do-not-contact table your campaign tool reads. It keeps the check off the send path; the trade-off is up to a day between a data update and your tool seeing it.
The litigator fields appear only when litigatorFilter: true is set. A match also sets blackList and action, so SMS logic that already suppresses on action needs no changes. Absent DNC fields mean that check didn't run (not checked), never clear.
| If the response shows | Field | Do this |
|---|---|---|
| Known TCPA litigator | litigator = "true"reason | Suppress for calls and texts. action is already "unsubscribe", with reason "Associated with TCPA Litigator DO NOT CONTACT". |
| Litigator, plaintiff or agitator | litigator_type | Treat all three the same: the type is how the match is classified in our data, and the action is identical. |
| A name on record | litigator_name | Potentially sensitive. Keep it only where you need it, don't log it unnecessarily, and never show it in customer-facing UI. Not every match has a name. |
| Not a litigator | litigator = "false" | Carry on with your other rules: line type, deactivation and the blacklist still decide action. |
| Blacklisted, no litigator match | blackListreason | Suppress. Our internal blacklist is separate from the litigator data; reason says "Blacklisted Subscriber". |
| State DNC or complainer match (free checks) | dncStateResult = STATE DNCdncComplainerResult = DNC COMPLAINER | A DNC match never changes action. Suppress unless you hold consent. If dncStateChecked is absent, the state wasn't checked. |
One credit for the lookup and one for the litigator check. The litigator fields fire, blackList is set, and action is forced to "unsubscribe", so the number never reaches your campaign.
Highlighted fields: action, reason, blackList, litigator, litigator_type, litigator_name.
{
"success": true,
"credits_used": 2,
"data": {
"subscriber": "2125550147",
"optDate": "2026-10-08T21:56:03.699Z",
"action": "unsubscribe",
"deliverable": "false",
"reason": "Associated with TCPA Litigator DO NOT CONTACT",
"nanpType": "mobile",
"blackList": "true",
"dip": "success",
"dipLrn": "2125550147",
"dipPorted": "false",
"dipOcn": "6010",
"dipCarrierSubType": "WIRELESS",
"dipCarrier": "AT&T",
"dipCarrierType": "mobile",
"litigator": "true",
"litigator_type": "litigator",
"litigator_name": "Jane Example",
"geoState": "NY",
"geoCity": "new york",
"geoCountry": "US",
"timezone": "America/New_York",
"tzOffset": 5,
"geoSource": "area-code",
"error": "false",
"doNotSms": "true"
}
}Each scrubbed number is 2 credits: 1 for the lookup, 1 for the litigator check. On a CSV upload, duplicates are billed once. State DNC and complainer checks never add credits. Computed from the published plans.
action: "unsubscribe" and blackList: "true" on every matchNot legal advice.
No. It runs in the same call as the live carrier dip, and the litigator fields come back in the same response.
No. Even a scrubbed number can be wrong to contact if you do not have the underlying consent. Treat litigator data as one safety layer on top of your consent records, not a substitute.
The litigator data is refreshed daily. We do not publish a per-record timestamp.
One extra credit per lookup it is enabled on, so a scrubbed lookup is 2 credits. On a CSV upload it is +1 credit per unique number.
They describe how the match is classified in our source data. All three carry the same recommended action, "unsubscribe", so treat them the same.
Not the litigator scrub itself. The free state DNC and complainer checks cover 38 states plus DC and our national complainer list; the National Do Not Call Registry is yours to scrub through the FTC.
Add litigatorFilter: true to any lookup, or tick the litigator scrub on a CSV upload.