High Performance Litigator API

The Litigator API is a specialized, high-performance endpoint for checking if phone numbers are associated with known TCPA litigators.

This API only checks the litigator list. It does not check Federal/State DNC databases, line type, Internal DNC, EBR, or calling time restrictions. If you need full DNC checking, use the Full Scrub API instead.

When to Use This API

You need high-performance litigator checking only
You want to pre-screen numbers before full scrubbing
Your workflow only requires litigator identification

Endpoint

https://dataapi.dncscrub.com/v1.4/scrub/litigator

Authentication

Include your API key in the loginId header or as a query parameter.

Parameters

Parameter	Required	Description
`phoneList`	Yes	Comma-separated list of 10-digit phone numbers
`loginId`	Yes	Your API Key (header or query parameter)

If submitting more than 100 phone numbers, you must use HTTP POST with JSON body instead of HTTP GET.

Example: HTTP GET

curl --location --request GET \
  'https://dataapi.dncscrub.com/v1.4/scrub/litigator?phoneList=5039367187,7075276405&loginId=YOUR_API_KEY'

curl --location --request GET \
  'https://dataapi.dncscrub.com/v1.4/scrub/litigator?phoneList=5039367187,7075276405' \
  --header 'loginId: YOUR_API_KEY'

const response = await fetch(
  'https://dataapi.dncscrub.com/v1.4/scrub/litigator?phoneList=5039367187,7075276405',
  {
    method: 'GET',
    headers: { 'loginId': 'YOUR_API_KEY' }
  }
);
const data = await response.json();

Response

[
  {
    "Phone": 5039367187,
    "IsLitigator": true
  },
  {
    "Phone": 7075276405,
    "IsLitigator": false
  }
]

Example: HTTP POST (for 100+ numbers)

Use HTTP POST with a JSON body for large batches:

curl --location --request POST \
  'https://dataapi.dncscrub.com/v1.4/scrub/litigator' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "phoneList": "2675466417,5039367187",
    "loginId": "YOUR_API_KEY"
  }'

const response = await fetch(
  'https://dataapi.dncscrub.com/v1.4/scrub/litigator',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'loginId': 'YOUR_API_KEY'
    },
    body: JSON.stringify({
      phoneList: '2675466417,5039367187'
    })
  }
);

Response

[
  {
    "Phone": 2675466417,
    "IsLitigator": true
  },
  {
    "Phone": 5039367187,
    "IsLitigator": true
  }
]

Response Fields

Field	Type	Description
`Phone`	Number	The phone number that was checked
`IsLitigator`	Boolean	`true` if the number is associated with a known litigator, `false` otherwise

Processing the Response

const results = await response.json();

const litigators = results.filter(r => r.IsLitigator);
const safe = results.filter(r => !r.IsLitigator);

console.log(`Litigators found: ${litigators.length}`);
console.log(`Safe numbers: ${safe.length}`);

// Take action on litigator numbers
litigators.forEach(r => {
  console.log(`WARNING: ${r.Phone} is a known litigator!`);
});

Security Best Practice

For additional security, pass the loginId in the HTTP header instead of the query string:

curl --location --request GET \
  'https://dataapi.dncscrub.com/v1.4/scrub/litigator?phoneList=5039367187,7075276405' \
  --header 'loginId: YOUR_API_KEY'

This prevents the API key from appearing in server logs and browser history.

Example Use Case

The following diagram illustrates a common workflow for businesses collecting opt-in leads, showing how the Litigator API and Reassigned Authority API work together to maintain TCPA compliance:

Workflow Summary

At checkout - When a customer opts in to receive marketing messages, immediately scrub against the Litigator List to avoid known litigators
Save the lead - Store the opt-in with the consent date
Wait 30 days - Phone numbers can be reassigned at any time; waiting helps identify reassignments
Scrub against Reassigned List - Before contacting, check if the number has been reassigned since consent was given
Optional re-check - Scrub against the Litigator List again (litigator status can change)
Repeat monthly - Continue this process every 30 days to maintain compliance

⌘I

Getting Started

Full Scrub

Litigator-Only Scrub

Reassigned Scrub

Call Deliverability (TrustCall)

Data Enhancement

GeoScrub

Other APIs

Code Examples

Litigator API

High Performance Litigator API

When to Use This API

Endpoint

Authentication

Parameters

Example: HTTP GET

Response

Example: HTTP POST (for 100+ numbers)

Response

Response Fields

Processing the Response

Security Best Practice

Example Use Case

Workflow Summary

​High Performance Litigator API

​When to Use This API

​Endpoint

​Authentication

​Parameters

​Example: HTTP GET

​Response

​Example: HTTP POST (for 100+ numbers)

​Response

​Response Fields

​Processing the Response

​Security Best Practice

​Example Use Case

​Workflow Summary

High Performance Litigator API

When to Use This API

Endpoint

Authentication

Parameters

Example: HTTP GET

Response

Example: HTTP POST (for 100+ numbers)

Response

Response Fields

Processing the Response

Security Best Practice

Example Use Case

Workflow Summary