July 2026

We're updating how the Property Search API bills count-only requests. As of the effective date below, a Property Search request that passes take: 0 to retrieve only counts or summaries is billed for one property record.

Previously, Property Search requests with take: 0 were not billed. Going forward, a take: 0 request is billed for one property record. This does not change billing for any other request: a request with take greater than 0 is still billed only for the property records it returns, and a request that returns no matching properties is not charged.

This applies to both:

The per-record charge is still determined by the datasets included in your request. If no dataset can be resolved for a request, the single record is billed at the basic property dataset rate.

Aggregate-only Property Search requests (counts, summaries, market sizing) still touch the same search infrastructure as a full property pull. As usage of the take: 0 pattern has grown, the infrastructure cost of fulfilling those requests has grown with it. The minimum 1-record charge lets us continue to offer aggregate access at a predictable, dataset-aligned rate.

Examples of how requests are billed after the change:

If you use take: 0 to retrieve counts or summaries at high volume, you may see new line items on your invoice corresponding to one record per such request.

No code changes are required. If you currently use take: 0 for aggregate-only requests, you can keep doing so. Just budget for one billed record per request at the appropriate dataset rate.

If you'd like to confirm the rate that will apply to your usage pattern, contact our team using the links below.

This change is effective July 7, 2026. The one-record charge for take: 0 requests applies to Property Search requests made on or after this date. If you'd like to confirm how it affects your usage, contact support using the links below.

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