Blacklist / DNC API
Pingtree integrates with Blacklist Alliance to check lead phone numbers against Do Not Call (DNC) registries and blacklists before accepting or distributing them. This helps protect your campaigns from compliance risk and reduces wasted spend on leads you cannot legally contact.What is the Blacklist / DNC Check?
The Blacklist Alliance lookup queries a comprehensive database of phone numbers that are registered on federal or state DNC lists, or that have been flagged through litigation history. When a lead submits a phone number, Pingtree sends it to the Blacklist Alliance API in real time and stores the result on the lead record. The result is saved in theblacklist_alliance_check field and can be one of:
| Value | Meaning |
|---|---|
clean | The number is not on any blacklist and is safe to contact. |
blacklisted | The number is on a DNC list or has been flagged. |
NotProcessed | The check was skipped or encountered an error (e.g. timeout). |
Configuration
The Blacklist / DNC integration is configured at two levels: Campaign and Source.Campaign-Level Configuration
Configuration Path:Campaign > Single View > Integrations Tab > Blacklist Alliance API
Enabling the integration at the campaign level applies the DNC check to all leads that flow through the campaign. You can optionally provide your own Blacklist Alliance API key. If no key is provided, Pingtree uses the platform’s shared key.
Configuration Options
| Option | Description |
|---|---|
| Enable Integration | Toggle to activate the Blacklist Alliance check for this campaign. |
| API Key | Your personal Blacklist Alliance API key. Leave blank to use Pingtree’s default key. |
| Validation Rule | Choose what to check: phone (default). Phone validation queries the Blacklist Alliance /lookup endpoint using the lead’s phone number. |
Source-Level Configuration
Configuration Path:Sources > Single View > Integrations Tab > Blacklist Alliance API
You can also configure the Blacklist / DNC check at the individual source level, allowing you to apply different behavior per traffic source.
Configuration Options
| Option | Description |
|---|---|
| Enable Integration | Toggle to activate the check for leads submitted through this source. |
| API Key | Source-specific API key (overrides the campaign-level key). |
| Store Rejected Lead | If enabled, leads flagged as blacklisted are still stored in the system. |
| Force Process Lead | If enabled, blacklisted leads are stored and sent through campaign distribution regardless of their DNC status. |
How It Works
- A lead is submitted through the Lead Post API, Ping API, or Post API.
- If the Blacklist Alliance integration is enabled and not skipped, Pingtree sends the lead’s phone number to
https://api.blacklistalliance.net/lookup. - The API response is evaluated, and the result is stored in the
blacklist_alliance_checkfield on the lead record. - If the number is flagged and neither Store Rejected Lead nor Force Process Lead is enabled, the lead is rejected and not stored or distributed.
Note: The check runs after phone/email validation and fraud detection but before lead distribution. You can bypass it by passingskipBlackListAlliance: trueorskipAllIntegrations: truein your API request.
Lead Data Field
| Field | Description |
|---|---|
blacklist_alliance_check | The DNC check result: clean, blacklisted, or NotProcessed. |
Use Cases
- Compliance: Automatically reject phone numbers on federal or state DNC registries before distribution.
- Lead Quality: Reduce wasted buyer spend by filtering leads that cannot legally be contacted.
- Selective Enforcement: Use Store Rejected Lead to keep DNC records for reporting while still blocking their distribution.
- Audit Trail: The
blacklist_alliance_checkvalue is stored on every lead, giving you a clear audit record of which leads were checked and what result was returned.
Tip: If you are running campaigns where TCPA compliance is critical, combine the Blacklist / DNC check with TrustedForm or Jornaya to build a complete compliance stack.