Real Contact API 1.1 vs. Real Contact API 2.0: What’s Changed and How to Upgrade

If you’re already using Real Contact API to verify lead data, you’ve probably wondered what 2.0 actually changes. 2.0 builds directly on what 1.1 already does, adds an IP intelligence layer for evaluating lead legitimacy, and reorganizes the response in a way that’s more readable. Here’s a side-by-side breakdown of what’s different and how to start using it.

What’s Real Contact API? #

Real Contact API is Trestle’s comprehensive, real-time lead verification API. It verifies phone numbers, emails, address data, provides name matches, and returns A–F contact grades so you can prioritize leads by who’s most likely to be reachable and who they say they are.

With Real Contact 2.0, you get:

• Refined phone contact grading
• New IP-based intelligence checks
• A reorganized JSON response

Together, they help you evaluate not just whether a lead is contactable and who they say they are, but whether the lead itself appears legitimate.

What’s new in Real Contact API 2.0? #

There are three meaningful changes between 1.1 and 2.0. None of them removes existing functionality. Everything you rely on in 1.1 is still in 2.0.

1. IP-based Intelligence Checks #

Real Contact 2.0 introduces a new ip_address object in the response with two attributes: trust_score (a 0–100 score evaluating the legitimacy of an interaction based on the user’s IP) and ip_distance_to_address (the approximate mileage between the user’s IP location and their provided physical address).

These signals help you evaluate whether the person behind a form submission or signup appears genuine, not just whether their contact data is valid. That distinction matters because lead data can be real and verifiable while the submission itself is fraudulent. Bots cycling through stolen identity data, residential proxies masking traffic origin, and recycled lead submissions can all produce contact data that looks clean on the surface.

2. Enhanced Phone Contact Grading #

The A-F grading system has been refined to prioritize higher connect rates over raw volume. An analysis of the refined phone contact grades revealed companies received 5-15% fewer Grade A and B contacts, but right party contact rates improved by approximately 0.5-1%. In practice, if you were previously dialing 10,000 Grade A/B contacts, you’d now target around 9,000 higher-quality contacts with a better chance of reaching the right person. Lower outbound dialing costs, higher contactability.

If you want the full grading breakdown, the Real Contact API grading explainer covers what each grade means and how to use them.

3. Reorganized Response Structure #

The JSON response has been restructured for readability. All response fields are now nested under an input object, contact grades have been moved to the top of each relevant object, and a few add-on field names have been updated (more on that below).

Side-by-Side Comparison #

Here’s a quick comparison of the two versions:

Pricing stays the same. You get the IP attributes and refined grading at no additional cost.

Response Structure at a Glance #

Here’s what the response structure looks like for each version:

Real Contact 1.1 #

{
  "phone.is_valid": true,
  "phone.activity_score": 100,
  "phone.linetype": "Mobile",
  "phone.name_match": true,
  "phone.contact_grade": "A",
  "email.is_valid": true,
  "email.name_match": true,
  "email.contact_grade": "A",
  "address.is_valid": true,
  "address.name_match": true
}

{
  "phone.is_valid": true,
  "phone.activity_score": 100,
  "phone.linetype": "Mobile",
  "phone.name_match": true,
  "phone.contact_grade": "A",
  "email.is_valid": true,
  "email.name_match": true,
  "email.contact_grade": "A",
  "address.is_valid": true,
  "address.name_match": true
}

Real Contact 2.0 #

{
  "phone": {
    "contact_grade": "A",
    "is_valid": true,
    "activity_score": 90,
    "line_type": "Mobile",
    "name_match": true
  },
  "email": {
    "contact_grade": "A",
    "is_valid": true,
    "name_match": true
  },
  "address": {
    "is_valid": true,
    "name_match": false
  },
  "ip_address": {
    "trust_score": 90,
    "ip_distance_to_address": 5
  }
}

{
  "phone": {
    "contact_grade": "A",
    "is_valid": true,
    "activity_score": 90,
    "line_type": "Mobile",
    "name_match": true
  },
  "email": {
    "contact_grade": "A",
    "is_valid": true,
    "name_match": true
  },
  "address": {
    "is_valid": true,
    "name_match": false
  },
  "ip_address": {
    "trust_score": 90,
    "ip_distance_to_address": 5
  }
}

Three things to notice: 

1. Fields are now grouped under their parent object (phone, email, address, IP) instead of dot-notated at the root.
2. The naming convention of add-ons have also changed:
   1. is_litigator _risk is now phone_is_litigator_risk
   2. email.is_deliverable is now email_is_deliverable
   3. email.age_score is now email_age_score
3. Contact_grade sits at the top of each object, so it’s the first thing you read.
4. The new ip_address object brings trust_score and ip_distance_to_address into the same response.

Who’s on 1.1 and Who’s on 2.0? #

Real Contact 2.0 launched in April 2026 and is the default for all new accounts created on or after that date, including trial users, self-serve customers, and enterprise accounts.

You’ll stay on Real Contact 1.1 if any of these apply:

• Your account was created before April 22, 2026.
• You’re a new user added to an existing enterprise account that’s still on 1.1 (you inherit the account’s current version).
• You’re connecting to Real Contact through a third-party integration like ActiveProspect or Apollo.

There’s no restriction on moving from 1.1 to 2.0. Any existing customer can request the upgrade.

How to Upgrade to Real Contact 2.0 #

The upgrade itself is straightforward. To request access:

1. Reach out to your Trestle account executive, or email support@trestleiq.com to request the upgrade.
2. Fill out a “Contact Us” form and request an upgrade to Real Contact API 2.0.
3. Reach out to Trestle representatives on a website live chat. 
4. Use the Book a Meeting feature under your My Account tab to connect with your Trestle representative (for self-serve and trial users only).

If you want a deeper walkthrough of the IP attributes, including how to interpret trust_score and ip_distance_to_address together, this guide covers benchmark thresholds and recommended use cases.

Should You Upgrade to Real Contact 2.0? #

If you’re already happy with 1.1 and don’t need IP-based intelligence, there’s no urgency. 1.1 remains a reliable lead verification tool. That said, if you’re seeing suspicious lead patterns, dealing with form abuse or signup fraud, or want sharper grade precision to cut outbound dialing waste, 2.0 is built for those workflows specifically.

The IP attributes are most valuable when you need to evaluate not just whether a contact is real, but whether the submission itself looks legitimate. That’s a different question than contact data verification can answer on its own, and it’s the gap 2.0 is designed to close.

Ready to move to Real Contact 2.0? Contact us to request the upgrade, or start your free trial if you’re new to Trestle. Check out the API documentation here.