Every BatchData API release note, grouped by the quarter it shipped in. Newest first.
Q3 2026 (July - September)
Property Search now accepts name-based criteria, so an integration can locate records by a current owner's name using the containsWords operator, or identify properties that a given party has previously sold. Supplying both a first and a last name matches only where both names sit on the same owner record, and the owner-name match block returns one consolidated count in place of a separate count for each name part. Requests that pass take=0 to retrieve only a count now carry a one-record minimum charge, which cost estimates should account for.
Owner-Name Search Now Matches Both Names on the Same Owner - August 2026: Supplying both owner.firstName and owner.lastName now matches only when both names sit on the same owner record, and the ownerNameMatch response block replaces its two per-part counts with a single ownerNameMatchCount.
Previous-Owner Property Search - July 2026: Find properties a party previously sold by matching their name with the new previousOwner.fullName search criterion.
Owner-Name Property Search - July 2026: Search for a property by its owner's name with the new containsWords operator, and confirm whether a specific person is on the owner record at a known address with the new exact address-match mode.
Property Search: New Minimum 1-Record Charge for take=0 Requests: Property Search requests that pass take=0 (count-only requests) are now billed for one record at the resolved dataset rate. Here's what's changing and how to anticipate it on your invoice.
Q2 2026 (April - June)
Two endpoints were added for identifying people and prospective buyers. Reverse Skip Trace returns persons and their property addresses from a phone number or email address, and the Buy Box endpoint ranks the investors most likely to purchase a specified property. A comps dataset became available for comparable-property analysis at a lower per-record cost, 22 attributes were added to Property Search and Property Lookup responses, and three wallet endpoints report account balance, consumption, and card transaction history. Account administrators can now determine which datasets OAuth MCP tokens return, which governs both data access and per-record billing from one place.
New Property Attributes Now Available, June 2026: 22 new building, deed, mortgage/lien, contact, and demographic attributes are now returned in Property Search and Property Lookup responses.
Reverse Skip Trace API, June 2026: Look up persons and their property addresses by phone number or email. Available now.
New: Buy Box endpoint for investor discovery: A new endpoint that returns the investors most likely to buy a subject property, synthesized from nearby comparable sales. Billed per matched investor profile returned.
New: comps dataset for low-cost comparable-property analysis: A new low-cost dataset for comparable-property (CMA) analysis: 24 comp-analysis attributes. A token with Basic Property Data plus comps bills $0.03 per record, about 3x less than a core-only token at $0.10.
New: wallet endpoints for balance, consumption, and credit card history - June 2026: Three new GET endpoints under /api/v1/wallet/ for tracking your wallet balance, consumption breakdown, and credit card transaction history. All three are free to call. Includes the scoped-token best practice.
Customize Datasets for OAuth MCP Connections - April 2026: Account admins can now control which property datasets are returned by OAuth-provisioned MCP tokens, managing both data access and per-record billing from a single page.
Q1 2026 (January - March)
Metropolitan area data became available on both the response and the query side of the API, as six CBSA, CSA, and Metro Division fields in the Core dataset and as matching Property Search filters. OAuth authentication became available for MCP connections, removing the need to configure an API token, and a set of Property Search tools was added to MCP. Property Lookup now accepts unitNumber and unitType as dedicated address fields, and async endpoints return a requestId so a webhook response can be correlated with the request that produced it. String values for distance parameters were deprecated.
Metro Area Fields in Core Dataset — March 2026: Learn about the six metropolitan area fields now included in Core property data, including CBSA, CSA, and Metro Division classifications.
New Property Search Filters — Metro Area (CBSA, CSA, Metro Division): Search for properties by metropolitan statistical area using CBSA, CSA, and Metro Division codes and names.
OAuth Authentication for MCP Server — January 2026: Connect your AI assistant to BatchData with a simpler, more secure authentication method. No API token configuration needed.
API Documentation Updates — January 2026: Release notes covering simplified Property Lookup address input, land use code search documentation, and new building search filters.
Property Lookup API: unitNumber and unitType Now Supported as Separate Fields - March 2026: The Property Lookup API now accepts unitNumber and unitType as dedicated address fields. Both the new separate-field pattern and the existing embed-in-street pattern are supported.
Deprecation Notice: String Values for Distance Parameters - January 2026: Important notice about the deprecation of string values for distance parameters in the BatchData Property Search API.
Async API Request ID Correlation - January 2026: New requestId field for async endpoints enables reliable correlation between API requests and webhook responses.
Property Search MCP Tools Release Notes - January 2026: Release notes for the new Property Search MCP tools including search_properties_count, search_properties_preview, search_properties_page, and comparable_property pagination updates.
Q4 2025 (October - December)
The BatchData MCP server and the V3 Skip Trace API became generally available. Property Monitoring was introduced for tracking changes to a saved set of properties without repeated polling, and the Datasets and Custom Projections API allows a response to be limited to the fields an integration actually consumes. Address Auto-Complete accepts longer queries and retries them normalized when there is no exact match, and Skip Trace excludes property addresses outside the United States from billing and returns mobile numbers first.
Datasets and Custom Projections API Release Notes - December 2025: Choose which property datasets and fields a response returns, using named datasets or a custom projection.
Property Monitoring API Release Notes - December 2025: Track changes to a saved set of properties and receive updates without repeated polling.
Address Auto-Complete API Release Notes - November 2025: Query strings now accept up to 50 characters rather than 25, and an address that returns no exact match is normalized and retried, so longer or unevenly formatted addresses still return suggestions.
Skiptrace API Release Notes - November 2025: Property addresses outside the United States now return no match and are not billed, and phone numbers in responses are ordered to place mobile numbers ahead of landlines, which improves contact rates.
BatchData V3 SkipTrace API Now Available: General availability release announcement for the V3 skip trace API endpoints
BatchData MCP Server Now Available - November 2025: Announcing the general availability (GA) release of the BatchData MCP server