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

39
  • Everything to Know About Source ID
  • 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 Real Contact API 2.0
View Categories

Everything to Know About Real Contact API 2.0

6 min read

Trestle’s Real Contact API verifies phone, email, and address data in real-time, returning phone and email contact grades so teams can assess lead contactability and connect with the right people faster. Now, we’re introducing Real Contact API 2.0, with new IP-based intelligence, enhanced phone grading, and a more intuitive response structure.

What is Real Contact API 2.0? #

Real Contact API 2.0 is an evolution of our core identity verification product. While Real Contact 1.1 focuses primarily on whether a contact’s phone, email, and identity are contactable and who they say they are, version 2.0 adds a risk intelligence layer. Real Contact API already answers two core verification questions, “Is this lead real?” and “Is this lead contactable?” By integrating IP-based checks, we now also answer, “Does this specific interaction (i.e., lead, signup, contact) appear legitimate?”

What new features are included?  #

Real Contact 2.0 introduces three major enhancements:

  • IP-based Intelligence: A new ip_address object in the response provides two new attributes: trust_score and ip_distance_to_address. These help you evaluate the authenticity of the interaction and how closely the lead’s IP location matches their provided address.
  • Refined Phone Contact Grading: We’ve improved the grading system to increase precision when identifying real, contactable leads. 
  • Intuitive Response Structure: The response JSON has been reorganized to make it easier to interpret and integrate into your existing workflows.

What is IP trust_score? #

The trust_score is a value from 0 to 100 that indicates the legitimacy of an interaction based on the user’s IP address. It evaluates network type (VPN, proxy, data center), IP reuse patterns, and historical behavior.

Accurately assessing an IP address requires understanding it in the full context of its network characteristics, metadata, and real-world usage patterns, so our model-based approach is far more effective than static rules. Rigid rules like blanket blocking of VPN or proxy IPs lack the nuance to distinguish between legitimate users and risky traffic, often leading to false positives that penalize good users. 

That’s why Trestle has built our own IP Trust Score trained on real world outcomes, to holistically evaluate a user’s IP address and allow for intelligent decisioning at the trust threshold most relevant to your business needs. 

How should I interpret IP trust_score? #

The model is calibrated to provide clear, actionable tiers of trustworthiness: 

ScoreInterpretation
>30High trust. There are strong signals that this interaction is genuine.
30 or belowLow trust. There are signals of potential risk, such as the use of anonymizing services, high device sharing, or suspicious activity patterns. 

These ranges are designed to work out of the box for common use cases in typical industries we serve, enabling you to quickly optimize risk decisioning with minimal setup. We highly recommend benchmarking the score against known conversion, fraud, or engagement outcomes to define custom thresholds that align with your specific risk tolerance and business goals.

What is the ip_distance_to_address attribute?  #

The ip_distance_to_address attribute indicates the approximate distance (in miles) between the user’s IP location and their physical address to surface location mismatches.

How should I interpret the ip_distance_to_address attribute? #

DistanceInterpretation
0 – 50 MilesHigh alignment between IP and physical address.
50 – 200 MilesUser may be connecting from a nearby city or mobile gateway.
>200 MilesPotential mismatch or deliberate misrepresentation of location.
NULLResult of missing data or low geolocation precision.

How should I make decisions based on IP intelligence? #

IP intelligence signals can help teams identify suspicious traffic patterns, flag geographic mismatches, and prioritize legitimate leads. It’s important to view IP intelligence in combination with other attributes, not as standalone fraud indicators. 

Our IP distance to address attribute indicates location alignment, but legitimate users may appear geographically distant due to VPNs, mobile networks, travel, or corporate gateways. Alternatively, VPN and proxy geolocation can return highly precise coordinates, even when they don’t reflect the user’s true location. A low ip_distance_to_address value doesn’t guarantee the user is actually nearby, it might simply mean the VPN exit node is close to the provided address. That’s why it’s crucial to evaluate ip_distance_to_address alongside the trust_score attribute. 

trust_scoreip_distance_to_addressInterpretation Recommendation
<=30>=200 milesLow trust. Strong risk signals with significant location mismatch. Do not buy or contact these leads. 
<=30<200 milesLow trust. Risk signals present, though location is reasonably aligned. Treat as lower priority.
>30>=200 milesModerate trust. Trust signals are strong, but location mismatch introduces uncertainty. Proceed outreach with caution.
>30<200 milesHigh trust. Consistent behavior with strong location alignment. Prioritize these leads as per the contact grades. 

Please note: These benchmarks are simply a starting point. Your ideal score thresholds will likely change based on your industry, lead source, and existing validation layers. We recommend analyzing these signals against your historical data to align these thresholds with your use case, or schedule a call with usto determine what the ideal benchmarks may be for your specific use case. 

What are the new phone contact grades?  #

We’ve refined our phone contact grading to help you prioritize leads more effectively:

  • Grade A: Valid, active mobile phones with high-confidence name matches. Prioritize these first.
  • Grade B: Valid/active landlines with name matches OR mobile phones with lower-confidence matches.
  • Grade C: Lower activity or weaker identity alignment. Best for automated nurture workflows or after higher grades are exhausted.
  • Grade D: High “wrong party contact” risk. Pursue only if higher grades are exhausted.
  • Grade F: Likely disconnected, premium numbers, or known TCPA litigators. Remove these from your lists.

Why change phone contact grading? #

Trestle’s Real Contact 1.1 grading is still reliable. That being said, we’re committed to continuously improving our products so the insights you rely on are as accurate and actionable as possible.

The new phone contact grading filters 5-15% of low-quality or illegitimate leads to improve contact rates by up to 1%. This helps teams waste less time and money while achieving better results, effectively lowering your outbound dialing costs.

Which users have access to Real Contact 2.0?  #

All new trial, self-serve, and enterprise accounts will get access to Real Contact 2.0 by default. Existing users on version 1.1 will remain on that version until they request an upgrade. To upgrade, contact your account executive or email support@trestleiq.com. 

Note: Real Contact 2.0 is a lead verification tool with added trust signals. It is not intended to be a standalone fraud-blocking system or a full risk decision engine.

If you need any assistance, don’t hesitate to reach out to support@trestleiq.com or book a meeting below.

Book a Meeting
Updated on April 21, 2026
Everything to Know About Phone Activity ScoreHow Trestle’s Activity Score is Different From HLR Lookups
Table of Contents
  • What is Real Contact API 2.0?
  • What new features are included? 
  • What is IP trust_score?
  • How should I interpret IP trust_score?
  • What is the ip_distance_to_address attribute? 
  • How should I interpret the ip_distance_to_address attribute?
  • How should I make decisions based on IP intelligence?
  • What are the new phone contact grades? 
  • Why change phone contact grading?
  • Which users have access to Real Contact 2.0? 
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