Q2 2026 Product and Development Recap
As we head into the second half of 2026, we’re excited to reflect on Q2. Our mission to provide industry-leading identity data APIs has driven several product launches and enhancements last quarter to help our customers improve their data quality, make operations more efficient, and achieve better results. Here’s a recap of the key highlights from Q2 2026:
Product Improvements
Real Contact API 2.0 Released:
We released Real Contact API 2.0 on April 22, and it’s now available upon request. Real Contact API has always addressed questions of contactability, like “Is this the right person?” and “Can I reach them?” Now, the addition of IP-based intelligence enables us to answer a more strategic, higher-value question: “Should this lead be contacted?”
This helps customers weed out bad leads before they ever reach a sales rep or agent. For our customers, that means fewer wasted outreach attempts, less time spent chasing contacts who were never going to convert, and a cleaner list to work from, so teams can focus their time on the leads most likely to close.
Phone-to-Address Match:
Real Contact 2.0 also introduced Phone-to-Address Match, which compares a phone subscriber’s location against the address on file to confirm who and where they are.
New and improved address match indicators now include:
- Match
- Street Match
- Postal Match
- City State Match
- Metro Match
- No Match
Metro matches can now also be identified using city/state or postal-code proximity without requiring a complete street address. Over the quarter, we extended this feature to support current and historical addresses, made it more resilient to input formatting (e.g., automatically normalizing full U.S. state names like “Washington” to their state code), expanded match coverage with additional data providers, and made it available in Batch Upload.
Spam Check Add-on:
Our new Spam Check Add-on is available now for Caller Identification API. The AI-powered signal evaluates phone metadata, caller reputation, and calling patterns to assess whether a phone number is likely associated with spam, robocalls, or high-risk activity.
The add-on returns “true” if the number points towards potential spam risk, or “false” if not. Customers can use it to route flagged calls to additional verification steps, prioritize interactions for review, or check it against their own numbers to protect their outbound calling reputation.
Updated Phone Contact Grades:
We rolled out a refreshed set of Phone Contact Grades in Real Contact 1.1, available immediately via custom attribute. The updated grading improves precision on Grade-A classifications and reduces the combined volume of A and B grades by approximately 10%, with an average contact rate improvement of 0.5–1%.
Improved Overall Phone Data Quality:
We improved phone number handling in Real Contact API and Phone Validation API this quarter, enhancing our carrier and line type identification, providing clearer messaging on phone number coverage, and expanding our internal data sources for caller ID lookups on domestic numbers.
Platform Enhancements
Interactive Usage and Error Graphs:
Usage and error graphs in the Developer Portal are now interactive for all users, with restored error-type breakdowns for faster troubleshooting.
Smarter Batch Uploads:
We revised our Batch Upload instructions for clarity, added direct CSV template downloads right inside the upload flow, and expanded the Real Contact API batch template to accept first name, last name, and secondary address line inputs for stronger matching. By the end of the quarter, Batch Upload also checks files for invalid phone number formatting upfront and warns customers before the batch runs, so issues can be caught and fixed before processing begins.
Billing and Wallet Management Enhancements:
We added direct Stripe receipt links to Wallet payment emails, proactive warnings as customers approach their monthly Wallet limit, and easier controls for enabling or disabling auto-refill.
Developer Portal and Integrations
Enhanced Signup Recommendations:
We improved the signup experience so recommended APIs populate faster, giving customers a more relevant starting point. New users may now be asked to complete a lightweight business verification step during onboarding, with clear in-product and email guidance throughout.
Clearer, More Actionable API Errors:
We standardized our API error responses across Real Contact API and Reverse Phone API, so common issues like an invalid API key, exceeded quota, or rate limiting now return a clear error code, message, and hint for resolving it.
Documentation Improvements:
This quarter, we verified Trestle’s public Postman and GitHub presences and focused on improving AI readability of our documentation. We corrected documentation across our API products, updated our public Postman collection to remove outdated references, and made error-handling guidance easier to find from each product’s documentation page.
Expanded Integrations:
We made meaningful strides in growing our integration ecosystem during Q2, including releasing a custom n8n node (n8n-nodes-trestle). This brings Trestle’s phone validation and contact verification solutions directly into n8n workflows, including real-time Phone Activity Scores, contact verification, risk checks, and A–F Contact Grading, without needing to write custom API integration code.
We also updated two existing integrations and published setup guides:
Looking Ahead
Looking back on Q2, we’re proud of the momentum behind Real Contact API 2.0, Spam Check Add-on, and the coverage and usability improvements we delivered alongside them.
In Q3, we’re focused on continuing to improve the developer experience, expanding our integrations, introducing new add-ons, and iterating on the accuracy of our existing products and signals.
