BatchData gives you property, owner and address data through an API. This app brings it into your Make scenarios, so you can find properties, enrich them with owner contact details, verify addresses and phone numbers, and react to property changes without writing code.
Typical uses:
- Build a list of properties that match your filters and send it to a spreadsheet, CRM or marketing tool.
- Look up one address and add the full property record, ownership and sale history to a lead.
- Find the owner's phone numbers and emails (skip trace) for a property, and check the numbers against Do Not Call and TCPA litigator lists.
- Clean up addresses before mailing, or turn an address into coordinates.
- Start a scenario the moment a property you are watching changes.
Support: support@batchservice.com
- Sign in to your BatchData account and create an API token. Tokens are available on plans with API access.
- In Make, add any BatchData module to a scenario.
- Next to Connection, click Add, paste the token into API token and save.
If the token is rejected, create a new one and try again. Use a sandbox token to try the app with sample data. Sandbox tokens return mock data and are not billed. Use a production token for real data. If you need help, contact support@batchservice.com.
| Module | What it does |
|---|---|
| Search Properties | Finds properties by location and filters such as property type, bedrooms, owner details and prebuilt quick lists. |
| Get Property Details | Returns the full record for one address, property ID, hash or APN. |
| Batch Look Up Properties | Returns full records for up to 100 addresses in one call. |
| Get Property Permits | Returns the building permits for one property, one result per permit. |
| Module | What it does |
|---|---|
| Skip Trace Owner (V1) | Owner contact details for a property, one result per person. |
| Skip Trace Owner (V3) | Owner contact details, one result per property with a list of persons. |
| Batch Skip Trace Properties (V3) | Skip trace for up to 100 properties in one call. |
| Reverse Skip Trace (Phone or Email) | Finds the person behind a phone number or email address. |
| Verify Phone Numbers | Checks whether phone numbers are valid and reachable. |
| Check Do Not Call | Checks phone numbers against the Do Not Call list. |
| Check TCPA Litigator | Checks phone numbers against known TCPA litigators. |
| Module | What it does |
|---|---|
| Verify Address, Batch Verify Addresses | Standardizes and validates one address, or up to 100 US addresses. |
| Autocomplete Address | Suggests addresses as you type. |
| Geocode Address | Turns an address into coordinates. |
| Reverse Geocode (Find Nearby Addresses) | Finds the addresses closest to a set of coordinates. |
| Module | What it does |
|---|---|
| Find Investors (Buy Box) | Finds likely investors for a subject property, based on nearby comparable sales. |
| Get Investor Properties | Lists the properties an investor holds. |
A search session remembers what it has already returned, so each run gives you only properties you have not received before.
| Module | What it does |
|---|---|
| Create or Advance Search Session | Starts a session, or returns the next properties from an existing one. |
| List Search Sessions | Lists the sessions on your team. |
| Delete Search Session | Deletes a session. |
A monitor reports when a property is added to it, removed from it or changed.
| Module | What it does |
|---|---|
| Create Property Monitor (Stream Delivery) | Creates a monitor that delivers to AWS Kinesis or Azure Event Hubs. |
| List Property Monitors, Get Property Monitor | Reads your monitors. |
| Delete Property Monitor | Deletes a monitor. |
| Module | Type | What it does |
|---|---|---|
| Watch New Search Sessions | Polling | Runs when a new search session appears on your team. |
| Watch New Properties in a Search Session (Billed) | Polling | Runs for each new property a session delivers. |
| Watch Property Monitor Events (Instant) | Instant | Runs when a property is added to, removed from or changed in a monitor. |
| Watch Property Monitor Events with Property Record (Instant, Billed) | Instant | The same, and adds the full property record to each event. |
| Module | What it does |
|---|---|
| Make an API Call | Calls any other BatchData API path with your connection. |
Search Properties, Get Investor Properties, Find Investors (Buy Box), Get Property Permits, List Search Sessions and Watch New Search Sessions have a Limit field. It is the total number of records you want. Make fetches them in pages of up to 100 and never asks for more than your Limit, so the Limit is also the most you can be billed for in one run. Search Properties and List Search Sessions also have Skip to start part-way through the results.
Each record comes out as its own bundle.
Your BatchData plan decides what each call costs. Each module's description in Make says how it is billed. In general:
- Search and lookup modules bill per record returned. Set a Limit to cap it.
- Skip trace modules bill per matched property.
- Address, phone and compliance checks bill per item checked.
- Autocomplete, geocoding and the modules that list, get or delete search sessions do not bill property records.
- Property monitors and the events they deliver are billed according to your BatchData plan.
- Get Property Permits bills per property requested, not per permit. A Limit above 100 sends more than one request.
- Watch New Properties in a Search Session (Billed) bills every property it delivers, on every scheduled run.
- Watch Property Monitor Events with Property Record (Instant, Billed) adds one property lookup per event.
For pricing questions, contact support@batchservice.com.
When you turn a scenario on, the instant trigger creates a monitor that delivers to that scenario's own Make webhook. When you turn it off, or delete the scenario, the monitor is deleted. You do not enter a callback URL.
Each event contains the event ID, property ID, address and parcel hashes, the IDs of the monitors that added or removed the property, and the time it changed. It does not contain the property record. Use the module with Property Record to add it. Use the event ID to skip repeats.
Good to know:
- You can have up to 5 monitors per team, so avoid many scenarios that each create one.
- A monitor cannot be edited. Delete it and create a new one.
- A new monitor can take up to 7 days to start delivering.
- Delivery is best effort, with 4 attempts per event, so the same event can arrive more than once.
- Make has no polling trigger for new monitors. Use List Property Monitors on a schedule instead.
Skip trace and phone modules return data only. You are responsible for following the TCPA and Do Not Call rules before you contact anyone. Skip trace leaves out phone numbers flagged as TCPA litigators unless you switch on Include phone numbers flagged as TCPA litigators.
Email support@batchservice.com.
The code in this repository is released under the MIT License (see LICENSE). The BatchData API and the data it returns are proprietary to BatchData (batchdata.io) and are subject to BatchData's terms of service. Development notes are in DEVELOPMENT.md.