Trestle - Identity Data Enrichment and Validation APIs Trestle - Identity Data Enrichment and Validation APIs Trestle - Identity Data Enrichment and Validation APIs Trestle - Identity Data Enrichment and Validation APIs
  • Products
        • Enrichment

        • Reverse Phone APIGLOBAL
        • Verify and enrich phone numbers
        • Reverse Address API
        • Verify and enrich address information
        • Caller Identification API
        • Identify and enrich caller information
        • Add-Ons

        • Litigator Check
        • Identify phone numbers associated with serial litigators
        • Email Deliverability
        • Confirm email inboxes accept mail in real-time
        • Spam Check
        • Flag phone numbers tied to high-risk calling activity
        • Email Age Score
        • Score how long an email has existed
        • Validation & Verification

        • Phone Validation APIGLOBAL
        • Validate phone numbers and identify disconnected numbers
        • Real Contact API
        • Verify phone, email, and address information
        • Address Validation API
        • Validate and normalize addresses
        • Assess Risk

        • Decision Console
        • Optimize identity verification for manual review
        • Decision Signals API
        • Automate identity verification for risk decisioning
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Solutions
        • Industries

        • B2B Contact Data
        • eCommerce
        • Insurance
        • Lead Generation
        • Real Estate
        • Communications
        • Use Cases

        • Verify and Prioritize Leads
        • Outbound Dialing Optimization
        • Assess Risk And Prevent Fraud
        • Inbound Call Routing and Verification​
        • Signup and Onboarding​
        • Optimize AI Voice Agents
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Pricing
  • Resources
        • API Documentation
        • Blog
        • Knowledge Base
        • Case Studies
        • Glossary
        • Partners and Integrations
  • Company
        • About Us
        • Why Trestle
        • Careers
        • Affiliate Program
        • Contact
  • Log In
  • Start for Free

Trestle Overview

19
  • Does Trestle Offer DNC Checks?
  • Does Trestle Have a Sandbox Environment To Test Integrations?
  • What is Trestle’s Coverage and Accuracy?
  • Which Countries’ Data Do You Have?
  • Does Trestle Normalize Phone Number Format?
  • How Do You Integrate Trestle’s APIs?
  • How Does Trestle’s API Pricing Work?
  • How Often is Trestle’s Data Updated?
  • How to Properly Sample a Test File and Evaluate Trestle
  • Understanding NPA-NXX and the Implications of Number Portability
  • Understanding Trestle’s Free API Trial and the API Access Request Process for Specific Products
  • What are the Response Times for Trestle’s APIs?
  • What are the Various Sources of Trestle’s Identity Data?
  • What are Trestle’s SLAs?
  • What Demographic Data Does Trestle Have?
  • What Is Our Global Phone Validation Coverage?
  • What is the Default and Max QPS Supported?
  • What Queries are Billable?
  • What Security Measures are Taken by Trestle?

Product Features

38
  • Everything to Know About IP Trust Scores
  • How to Check When an Email Address Was Made
  • Everything to Know About Spam Checks
  • Using IP Intelligence Checks to Verify Lead Legitimacy in Real Contact API
  • Everything to Know About Phone-to-Address Match
  • Real Contact API 1.1 vs. Real Contact API 2.0: What’s Changed and How to Upgrade
  • Everything to Know About Phone Activity Score
  • Everything to Know About Real Contact API 2.0
  • How Trestle’s Activity Score is Different From HLR Lookups
  • Everything To Know About Name Match Details
  • Everything To Know About Phone-to-Name Confidence Score
  • Everything To Know About Litigator Checks
  • Everything To Know About the Email Age Score Add-on
  • Everything To Know About the Email Deliverability Add-on
  • Explain Real Contact API Grading
  • Fine-Tuning Find Person API Results
  • How Can Trestle’s Email Data Be Used?
  • How Do I Determine Phone Validity?
  • How Do You Read Trestle’s Phone Activity Score?
  • How Does Our Real Contact API Name Matching Work?
  • How Does Trestle Assess Email Validity in Real Contact?
  • How is Trestle’s Phone Activity Score Calculated?
  • How To Read the Real Contact Data Assessment Report
  • International Reverse Phone API Explained
  • Line Type Fidelity and Confidence
  • Trestle API Response Attribute Ranking
  • Trestle Warnings – A Comprehensive Guide
  • Understanding the Difference: Phone Validity vs. Trestle’s Activity Score
  • What are the Different Address Types Returned by Trestle?
  • What Does a Name Match of Null Mean?
  • What Does the Carrier Name Mean?
  • What is the Difference Between CNAM and Trestle’s Smart CNAM API?
  • What is the Difference Between Fixed VoIP and Non-fixed VoIP?
  • What is the Difference Between Reverse Phone API, Caller Identification API, and Smart CNAM API?
  • What is the Link Date Associated with Phones and Addresses?
  • Why and When to Use Trestle’s Name Hint
  • Why Do We Return a Maximum of 100 Entities in Find Person API?
  • Why Does the Address Return as Invalid?

Integrations

22
  • HubSpot | Phone Validation App Integration Guide
  • ZoomInfo | Phone Validation, Real Contact, and Reverse Phone Integration Guide
  • Databar | Phone Validation Integration Guide
  • Make | Real Contact API Integration Guide
  • Make | Phone Validation API Integration Guide
  • Apollo | Phone Validation Integration Guide
  • HighLevel | Phone Validation Integration Guide
  • boberdoo | Real Contact API Integration Guide
  • Clay | Validate Phone Number Integration Guide
  • Clay | Verify Contact Integration Guide
  • HubSpot | Real Contact Phone Grading App Integration Guide
  • How Do I Use a HubSpot List To Grade My Contacts?
  • How Do I Use HubSpot Workflow Triggers To Grade My Contacts?
  • Lead Prosper | Phone Validation Integration Guide
  • Lead Prosper | Real Contact Integration Guide
  • Reverse Phone API Enrichment of Leads in Google Sheets via Zapier
  • Snowflake | Phone Validation Integration Guide
  • What is the Phone Validation Integration within ActiveProspect?
  • What is the Real Contact Integration within ActiveProspect?
  • Validate and Verify Leads with Trestle’s Phone Validation API in Sierra Interactive via Zapier
  • Validate Leads with Trestle’s Phone Validation API in LeadConnector via Zapier
  • Zapier | Grade Leads from a Google Sheet with Real Contact

Troubleshooting

9
  • How to Prevent 429 Errors by Sizing API Concurrency to Your QPS Limit
  • How to Fix 403 Forbidden Errors When Using Trestle’s APIs
  • Why Won’t My Email Work to Signup for Trestle?
  • Ruby Integrations: 403 Forbidden Errors
  • Getting 429: Too Many Requests Error – Why?
  • How to Remove or Deactivate a User in Trestle’s Developer Portal
  • How to Update Phone to Name/Address Linkage Records
  • Reviewing Usage Data
  • Why is the Name Associated with the Phone Incorrect?

Developer Portal

8
  • Business Verification Failed? Here’s What Documents You Need to Submit
  • How to Find and Download Your Receipt or Invoice
  • How to Monitor API Errors With Your Usage Graph
  • Batch Upload FAQ
  • Developer Portal Wallet Frequently Asked Questions
  • Export and Analyze Your Queries in Your Developer Portal Account
  • Getting Started with Trestle’s Developer Portal Wallet
  • Making Changes to Billing Settings for the Developer Portal Wallet

User Guides

9
  • Phone Validation in Java
  • Batch Upload Instructions
  • How Do I add Additional Members to My Trestle Account?
  • How to Handle Special Characters in API Queries
  • Phone Validation API with ASP.NET
  • Phone Validation with JavaScript and HTML: Leveraging Trestle’s API
  • Phone Validation API with PHP: Leveraging Trestle’s API
  • Phone Validation API with Python
  • Phone Validation API with React

Telephony Knowledge

9
  • Choosing the Right Number Lookup API
  • How to Identify Callers In Real-Time Using a Reverse Phone API
  • Why is Line Type Intelligence Important?
  • What is a “No Routes Found” Phone Message?
  • The Best Phone Validation API for Call Centers
  • How to Identify Disconnected Phone Numbers Automatically
  • What is a Phone Number Reputation Lookup?
  • What is a Carrier Number?
  • What is a Non-Fixed VoIP Phone?

Risk Suite Overview

8
  • How to Read Email Breach Reports and IP Abuse Reports in Decision Console
  • Everything to Know About Decision Signals API
  • How to Get Started With Decision Console
  • What is the Decision Overview and How Do I Read It?
  • What is an Attribute Card and How Do I Read It?
  • What is Link Builder and How Do I Use It?
  • Understanding Team and Account Management
  • FAQ and Troubleshooting: Decision Console
  • Home
  • Knowledge Base
  • Product Features
  • Everything To Know About Litigator Checks
View Categories

Everything To Know About Litigator Checks

4 min read

A litigator check flags phone numbers tied to known TCPA and consumer-protection litigators (both serial plaintiffs and their attorneys). Trestle’s Litigator Check Add-on is available in Phone Validation API, Real Contact API, and Caller Identification API. It refreshes litigation data daily from federal and state court filings, and automatically grades flagged numbers as F so they drop out of your outreach before you dial.

What is a litigator check? #

A litigator check flags any phone number that is part of a TCPA or similar consumer regulation litigation in the past. It covers both the plaintiff and the attorneys involved in the litigation. We provide Litigator Checks so businesses can avoid calling these potential serial litigators to prevent unnecessary litigation that can be a cost and resource drain. 

While TCPA is one of the prominent regulations for outbound dialing, we also flag other consumer protection litigators to ensure that we provide comprehensive coverage and minimize any risk to the business:

  • Telephone Consumer Protection Act (TCPA) 
  • Consumer Finance Protection Bureau (CFPB)
  • Fair Debt Collection Protection Act (FDCPA)
  • Fair Credit Reporting Act (FCRA)

This has a low hit rate, as expected, but businesses generally filter out these numbers from their dial lists. Many litigators involved in TCPA cases are known as serial litigators who actively look for violations, and who sometimes register new phone numbers to evade detection. Litigator Check Add-on also flags associated numbers, not just the ones already on record.

How is this litigator database built and maintained? #

We source this data from aggregators who monitor every litigation being filed in federal and state courts. It’s tedious work to review each filing, categorize it, and extract the plaintiff and attorney details, which then have to be standardized and made available via API calls. The data is updated daily, so you’re screening against the most recent filings rather than a stale list.

Because litigation is tracked at the person level rather than just the individual number on a case, the check can also surface additional numbers associated with a known litigator who may use alternative contacts.

What does TCPA non-compliance actually cost? #

The TCPA carries statutory damages of $500 per violation, rising to $1,500 per violation when the conduct is found to be willful or knowing (47 U.S.C. § 227(b)(3)). Damages are assessed per call or text, and statutory damages are uncapped, so a single bad list can scale into a serious number quickly.

The exposure is amplified by how these cases are litigated: nearly 80% of TCPA lawsuits are filed as class actions, with settlements that have ranged from $5M to $60M. A small population of serial litigators in your dial list can turn into an outsized, recurring legal cost. Screening them out before contact is one of the cheapest forms of risk reduction available to an outbound team.

How do we provide litigator checks? #

Litigator Checks are an add-on to Real Contact API, Caller Identification API, and Phone Validation API. Please reference the API docs for each API for guidance on how to update your integration.

How often should this check be performed? #

Every time a dial is performed and/or after 30 days since the last check done. Numbers change hands, and litigation might have happened recently since the first time this lead came through the door. For various reasons, we recommend checking the numbers for potential litigation. 

Does the Litigator Check Add-on have additional costs? #

Yes, it does. The pricing for the Litigator Check Add-on starts at $0.005/query, with volume discounts available.

Can Litigator Checks be included in Batch Processing? #

Yes, Litigator Checks are available when you process a batch file. A check box is available to select which add-ons you would like included.

Why aren’t Litigator Checks part of Real Contact API, Caller Identification API, or Phone Validation API by default? #

Our identity APIs serve multiple use cases, including fraud prevention, call center operations, and lead verification. Litigator checks are very specific to outbound dialing, so it didn’t make sense to include these in our response and impact all customers. Hence, the add-on can be enabled on a per-customer basis.

What is the typical hit rate? Or how many times do we typically see a litigator hit across our customers? #

We typically see around 1% hit rate across our customers.

Will this flag impact Real Contact API grades? #

Yes. If the Litigator Check Add-on has been enabled and phone.is_litigator_risk = TRUE, then the Phone Contact Grade is automatically set to F. This is because these leads are associated with known litigators or serial TCPA plaintiffs and should not be contacted.

If phone.is_litigator_risk = FALSE or NULL, there is no impact on the Phone Contact Grade.

Where does litigator screening fit in my outbound dialing workflow? #

Litigator screening isn’t a one-time cleanse. Numbers change hands and new cases are filed constantly. The most reliable approach is to screen at two points and recheck on a schedule:

StageWhen to run the checkWhy it matters
At onboarding / list ingestionWhen a new lead or list first enters your systemCatch known litigators before they ever reach a dialer or CRM segment
Pre-call (at the point of contact)Immediately before a dial or textCompliance is enforced at the moment of contact, when liability attaches
Periodic recheckEvery 30 days for numbers already in your systemAccounts for ownership changes and newly filed litigation

Litigator Check Add-on slots in alongside the rest of your contact-data stack. Use it in Phone Validation API to drop disconnected and invalid numbers, and Real Contact API to grade contactability A–F. For the full picture of a compliant, high-connect dialing operation, see our Outbound Dialing Optimization solutions and our guide to phone number reputation lookups, which covers related carrier-level compliance signals like spam/scam labeling.

Not sure how many litigators are hiding in your dial list? Upload a batch of records for a free data assessment and see your contact-data health before you dial. No signup or card required.

Updated on June 30, 2026
Everything To Know About Phone-to-Name Confidence ScoreEverything To Know About the Email Age Score Add-on
Table of Contents
  • What is a litigator check?
  • How is this litigator database built and maintained?
  • What does TCPA non-compliance actually cost?
  • How do we provide litigator checks?
  • How often should this check be performed?
  • Does the Litigator Check Add-on have additional costs?
  • Can Litigator Checks be included in Batch Processing?
  • Why aren't Litigator Checks part of Real Contact API, Caller Identification API, or Phone Validation API by default?
  • What is the typical hit rate? Or how many times do we typically see a litigator hit across our customers?
  • Will this flag impact Real Contact API grades?
  • Where does litigator screening fit in my outbound dialing workflow?
trestleLogo

Verified Identities. Trusted Interactions.

U.S. coverage for enrichment and verification.

Global coverage for phone validation and reverse phone.

Based in Bellevue, WA

Linkedin Github Postman

Company

  • About Us
  • Why Trestle
  • Careers
  • Affiliate Program
  • Contact

Products

  • Reverse Phone API
  • Reverse Address API
  • Caller Identification API
  • Phone Validation API
  • Real Contact API
  • Address Validation API
  • Batch Upload
  • Litigator Check Add-on
  • Free Lead Assessment

Use Cases

  • Outbound Dialing Optimization
  • Inbound Call Routing and Verification
  • Signup and Onboarding
  • Lead Verification
  • Optimize AI Voice Agents

Resources

  • Blog
  • Knowledge Base
  • Case Studies
  • Glossary
  • Data Dictionary
  • Changelog
  • Partners and Integrations

Developers

  • Developer Portal
  • API Documentation
  • API Live Status

Legal

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement
  • Service Level Agreement
  • Do Not Sell My Personal Information
Trestle - Identity Data Enrichment and Validation APIs
  • Products
        • Enrichment

        • Reverse Phone APIGLOBAL
        • Verify and enrich phone numbers
        • Reverse Address API
        • Verify and enrich address information
        • Caller Identification API
        • Identify and enrich caller information
        • Add-Ons

        • Litigator Check
        • Identify phone numbers associated with serial litigators
        • Email Deliverability
        • Confirm email inboxes accept mail in real-time
        • Spam Check
        • Flag phone numbers tied to high-risk calling activity
        • Email Age Score
        • Score how long an email has existed
        • Validation & Verification

        • Phone Validation APIGLOBAL
        • Validate phone numbers and identify disconnected numbers
        • Real Contact API
        • Verify phone, email, and address information
        • Address Validation API
        • Validate and normalize addresses
        • Assess Risk

        • Decision Console
        • Optimize identity verification for manual review
        • Decision Signals API
        • Automate identity verification for risk decisioning
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Solutions
        • Industries

        • B2B Contact Data
        • eCommerce
        • Insurance
        • Lead Generation
        • Real Estate
        • Communications
        • Use Cases

        • Verify and Prioritize Leads
        • Outbound Dialing Optimization
        • Assess Risk And Prevent Fraud
        • Inbound Call Routing and Verification​
        • Signup and Onboarding​
        • Optimize AI Voice Agents
        • Start using Trestle products today

          Get started for free—no credit card required

          Start Your Free Trial

  • Pricing
  • Resources
        • API Documentation
        • Blog
        • Knowledge Base
        • Case Studies
        • Glossary
        • Partners and Integrations
  • Company
        • About Us
        • Why Trestle
        • Careers
        • Affiliate Program
        • Contact
  • Log In
  • Start for Free