Address

Real Estate Search (Bulk) API

Real Estate Search (Bulk) runs the Real Estate Search for up to 50 addresses in a single call. Each address is answered on its own with its resolved address and its listing history, so a portfolio or a file of properties can be checked in one pass.

Up to 50 addresses per request, each as a GNAF ID, a single line of text or separate address fields
One date filter applied to the whole batch, and a check_id echoed on each result to match it back to your file

Get API access Talk to us

For developers

After the technical detail?

For the technical detail, go to the API documentation. It holds the request and response schema, the integration guides and the error codes for this endpoint.

Request and response schema
Address input modes and sandbox records

View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles

What the check gives you

Checking the listing history of many properties in one pass

Checking properties one at a time does not suit a portfolio review or a file of addresses. Real Estate Search (Bulk) takes up to 50 addresses in one request and returns a result for each. Every result carries the same fields as a single Real Estate Search, so the resolved addresses and their listing records can be written back to your system in one operation.

A result for every address sent

The results array holds one item per request item. Each item carries its own message, its resolved address with GNAF ID, the number of records found and the records themselves, most recent first.

Your own reference on each result

A check_id supplied on a request item is echoed on the matching result item, so each history lands against the right property in your file.

The listing events for each property

Each record is a sale listing, a sold event or a rental listing, with its date, price, estate agent, property type and the number of bedrooms, bathrooms and car spaces.

An address that cannot be found does not fail the batch

An item whose address could not be resolved is returned with the message Address not found, an empty address and no records. The other items in the batch are answered as normal.

How a check runs

Many properties in, one history per property out

The batch is sent as one request. Each address is resolved to the GNAF address database and searched in the Global Data property universe on its own, and the results come back together in the same response.

Each request item holds one address in one of three forms: a GNAF ID, a full address as a single string, or a structured address with the street address as a minimum. The forms are mutually exclusive within an item. The request holds between 1 and 50 items, and an optional date_from applies to every item.

What it costs

A monthly subscription, drawn down as you run checks

Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.

Volume-based pricing
No lock-in contract

How billing works

Subscribe monthly, spend it as credits

The monthly subscription arrives as credits on your account.
Each check draws down credits as it runs.
Checks beyond the included credits are billed per check.
Higher monthly volume moves you to a lower rate.

Talk to sales about volume

Related checks

Others in Address

Real Estate Search is the single-address form of this check. Address Validate Bulk takes the same batch approach for address standardisation.

Address Autocomplete API Address Lookup by Contact API Address Validate API Address Validate Bulk API Property Detail API Real Estate Search API

All Address endpoints

Questions

Questions we get asked about bulk real estate search

Do we need a developer to implement this?

Yes. Real Estate Search (Bulk) is a REST endpoint that takes a JSON array of up to 50 addresses and returns a JSON array of results, so a developer connects it to your data pipeline or batch job. A sandbox with a separate test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.

What does our system need to send?

A requests array of 1 to 50 items. Each item holds one address as a GNAF ID, as a full address in a single string, or as a structured address with the street address as a minimum and the suburb, state and postcode as separate fields. Each item may carry a check_id of your choosing. An optional date_from in YYYY-MM-DD format applies to every item in the batch.

What comes back for each address?

The check_id from the request, a message of Ok or Address not found, the resolved address with its GNAF ID, the number of records found, and the records sorted most recent first. Each record carries the listing type, property type, number of bedrooms, bathrooms and car spaces, the date, the estate agent and the price.

Where does the data come from?

Listing records are sourced from the Global Data Australian property universe. Text addresses are resolved against the GNAF address database. The reference documentation does not publish a refresh cycle for the listing data; each record carries the date of the event.

How large a file can we process?

Each request takes up to 50 addresses. The API allows 600 requests per minute by default, measured as a rolling average, and returns a 429 response above that rate. A higher limit can be requested through Global Data support.

Are the addresses we send stored by Global Data?

Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles.

Getting started

The first step to access is a conversation

New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.

Get API access Talk to us

Call 03 9948 4089, 9am–5pm AEST Monday to Friday

Encrypted in transit and at rest

Handled under the Australian Privacy Principles

ISO 27001 Certified