Skip to main content

BatchData V3 SkipTrace API Now Available

General availability release announcement for the V3 skiptrace api end-points

Written by Charles Parra
Updated over 3 months ago

Release Date: November 2025

We're excited to announce the release of our V3 Skip Trace API endpoint, delivering enhanced contact information for property owners with improved data coverage and more flexible TCPA compliance options. Access to this API is restricted to customers with a Skip Trace subscription.

What's New in V3?

1. Up to 3 Persons Per Property

The V3 endpoint now returns contact information for up to 3 persons per property, compared to the single person returned by the V1 endpoint.

Why this matters:

  • Better contact coverage: Capture multiple property owners or household members

  • Higher success rates: More contact options increase your chances of reaching the right person

  • Comprehensive household data: See all associated persons with ownership or residence connections

2. Enhanced Response Format

The V3 response structure provides richer data organization with detailed person-level information:

  • Multiple persons per property with clear ownership indicators

  • Improved contact data quality with verification status

  • Enhanced address history and validity indicators

  • Better organization of phone and email data

3. New TCPA Filtering Default Behavior

This is the most important change in V3: different default handling of TCPA-restricted phone numbers.

Understanding the includeTCPABlacklistedPhones Parameter

Both V1 and V3 endpoints now support the includeTCPABlacklistedPhones parameter, but with different default values that change the response behavior.

V1 Skip Trace (Original Endpoint)

Endpoint: /property/skip-trace (V1)

Default: includeTCPABlacklistedPhones = false

Behavior:

  • By default, phone numbers with TCPA restrictions are filtered out and will not appear in the response

  • You only receive "safe to call" phone numbers

  • To include TCPA-restricted phones with a compliance flag, set includeTCPABlacklistedPhones: true

Use this endpoint when:

  • You want pre-filtered results with TCPA numbers automatically removed

  • You prefer a simpler response without compliance flags

  • Your workflow doesn't require visibility into filtered TCPA numbers

V3 Skip Trace (New Endpoint)

Endpoint: /property/skip-trace (V3)

Default: includeTCPABlacklistedPhones = true

Behavior:

  • By default, phone numbers with TCPA restrictions are included in the response

  • Each phone object includes a tcpa boolean attribute:

    • tcpa: true = TCPA restricted, do not call

    • tcpa: false = Safe to call

  • You can programmatically filter TCPA-restricted numbers based on your compliance needs

  • To automatically exclude TCPA-restricted phones, set includeTCPABlacklistedPhones: false

Use this endpoint when:

  • You want full visibility into all available phone numbers

  • Your application handles TCPA filtering programmatically

  • You need flexibility to apply different compliance rules for different campaigns

  • You want to see which contacts were filtered for compliance reasons

TCPA Compliance: What You Need to Know

What is TCPA?

The Telephone Consumer Protection Act (TCPA) regulates telemarketing calls and includes penalties for violations. Individuals on TCPA litigator lists have a history of filing lawsuits against companies for TCPA violations.

Why the Different Defaults?

V1 (Conservative Approach)

  • Default filtering protects users by removing risky numbers

  • Simpler for users who don't need TCPA visibility

  • Reduces risk of accidental non-compliance

V3 (Flexible Approach)

  • Default inclusion gives users full data visibility

  • Clear tcpa flag enables programmatic filtering

  • Supports sophisticated compliance workflows

  • Maintains transparency about data availability

Important: Always Check TCPA Status

Regardless of which endpoint you use, never call phone numbers flagged with TCPA restrictions. Both endpoints provide this information to ensure compliance:

  • V1: Either filters TCPA phones automatically (default) or includes them with a tcpa flag (when includeTCPABlacklistedPhones: true)

  • V3: Includes all phones with a tcpa flag (default) or filters them automatically (when includeTCPABlacklistedPhones: false)

Migration Guide

Should You Migrate to V3?

Migrate to V3 if you need (Note that access to V3 is limited to users with a Skip Trace subscription and features enhanced capabilities compared to V1):

  • Multiple contact persons per property (up to 3)

  • Full visibility into available phone numbers with TCPA flags

  • Programmatic control over TCPA filtering

  • Enhanced response data structure

Stay on V1 if you prefer:

  • Single person per property (simpler response)

  • Automatic TCPA filtering without flags

  • Your existing integration is working well

Migration Checklist

If migrating from V1 to V3: Ensure that your account is upgraded to a Skip Trace subscription to access the V3 API.

  1. Update your endpoint URL

  2. Update response parsing logic

    • Handle up to 3 persons per property instead of 1

    • Process the enhanced response structure

  3. Review TCPA handling

    • Option A (Recommended): Accept the new default (includeTCPABlacklistedPhones: true) and filter TCPA phones in your application using the tcpa flag

    • Option B: Maintain V1 behavior by setting includeTCPABlacklistedPhones: false in your request options

  4. Update compliance workflows

    • Implement TCPA flag checking in your dialing logic

    • Ensure all phone verification includes the tcpa boolean check

    • Train staff on the new compliance indicators

Examples

Request Examples

V3 Request with Default TCPA Behavior (Includes TCPA Phones)

{
   "requests":[
      {
         "propertyAddress":{
            "street":"123 Main Street",
            "city":"San Francisco",
            "state":"CA",
            "zip":"94103"
         }
      }
   ]
}

V3 Request with V1-Style TCPA Filtering (Excludes TCPA Phones)

{
   "requests":[
      {
         "propertyAddress":{
            "street":"123 Main Street",
            "city":"San Francisco",
            "state":"CA",
            "zip":"94103"
         }
      }
   ],
   "options":{
      "includeTCPABlacklistedPhones":false
   }
}

Response Example

V3 Response (Default - TCPA Phones Included)

{
   "status":{
      "code":200,
      "text":"OK"
   },
   "results":{
      "persons":[
         {
            "name":{
               "first":"John",
               "last":"Smith"
            },
            "phoneNumbers":[
               {
                  "number":"4155551234",
                  "carrier":"AT&T",
                  "type":"Mobile",
                  "reachable":true,
                  "tcpa":false,
                  "dnc":false,
                  "score":100
               },
               {
                  "number":"4155555678",
                  "carrier":"Verizon",
                  "type":"Mobile",
                  "reachable":true,
                  "tcpa":true,
                  "dnc":false,
                  "score":95
               }
            ],
            "emails":[
               {
                  "email":"john.smith@example.com",
                  "verified":true
               }
            ]
         },
         {
            "name":{
               "first":"Jane",
               "last":"Smith"
            },
            "phoneNumbers":[
               {
                  "number":"4155559999",
                  "carrier":"T-Mobile",
                  "type":"Mobile",
                  "reachable":true,
                  "tcpa":false,
                  "dnc":true,
                  "score":90
               }
            ]
         }
      ]
   }
}

Notice:

  • 2 persons returned for this property

  • Each phone includes a tcpa boolean flag

  • Phone number "4155555678" has tcpa: true - do not call this number

  • Phone number "4155559999" has dnc: true - also do not call

Compliance Best Practices

  1. Always check both TCPA and DNC flags before making any calls

  2. Never call numbers with tcpa: true - these are known TCPA litigators

  3. Never call numbers with dnc: true - these are on the Do Not Call registry

  4. Verify reachability - only call numbers with reachable: true

  5. Document your compliance process - keep records of how you filter contacts

  6. Regular training - ensure your team understands TCPA and DNC compliance

Additional Resources

  • Do Not Call (DNC) Registry: Numbers on the national Do Not Call registry

  • Phone Reachability: Indicates whether the number is currently active

  • Litigator Flag: Person-level indicator (informational only - use phone-level tcpa flag for filtering)

Pricing

V3 Skip Trace follows the same pricing model as V1:

  • Each matched property with at least one person counts as a billable request

  • The response includes a matchCount indicating billable requests

  • Multiple persons per property do not increase the per-property cost

Resources

Frequently Asked Questions

Do I need a subscription to access V3?

Yes, the V3 Property Skip Trace API is only available to customers with a Skip Trace subscription. Pay-as-you-go accounts are limited to the V1 endpoint.

Can I use both V1 and V3 endpoints?

Yes, both endpoints remain available. Choose the endpoint that best fits your use case and access.

Will V1 be deprecated?

No immediate plans to deprecate V1. We will provide advance notice if this changes.

How do I filter TCPA numbers in my application?

When using V3 with the default behavior, iterate through the phoneNumbers array and exclude any phone with tcpa: true.

What if I want the old V1 behavior in V3?

Set includeTCPABlacklistedPhones: false in the request options to automatically filter TCPA phones.

Does the litigator flag replace the tcpa flag?

No. The litigator flag is person-level and informational. Always use the phone-level tcpa flag for filtering decisions.

Questions? Contact our support team at support@batchservice.com or visit https://help.batchdata.io for more information.

Related Articles
API Documentation Links
Understanding Your BatchData Property Skip Trace Results
BatchData MCP Server Now Available - November 2025
Skiptrace API Release Notes - November 2025
Async API Request ID Correlation - January 2026
Did this answer your question?