Address

Address Validate Bulk API

Address Validate Bulk applies the Address Validate rules to up to 200 addresses in a single call. Each address in the batch is answered on its own, so a file of customer records can be standardised against the GNAF address database in one pass.

Up to 200 addresses per request, each matched to the GNAF address database and returned with its GNAF ID
A check_id you supply is echoed back on each result, so every answer lands against the right record in 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
Correction rules and error codes

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

Standardising a file of addresses in one pass

Customer files accumulate addresses keyed in different formats and with different errors. Address Validate Bulk sends up to 200 of them in one request and returns a result for each. Every result carries the same fields as a single Address Validate call, so the standardised addresses and their GNAF IDs can be written back to your database in one operation.

A result for every address sent

The results array holds one item per request item, in the same order. Each item states whether the address is valid and carries its own matched address, score and list of changes.

Your own reference on each result

A check_id supplied on a request item is returned on the matching result item. Your system uses it to write each answer back to the correct record without relying on position.

The standardised address

A valid item's result includes the matched address.

Problems with one address do not fail the batch

An item that could not be matched is returned as not valid with an empty matched address. An item that hit an internal error is returned with an error field. The rest of the batch is answered as normal.

How a check runs

Many addresses in, one answer per address out

The batch is sent as one request. Each address is matched to the GNAF address database independently and the results come back together in the same response.

Each request item uses the same inputs as Address Validate: a street address plus a suburb or postcode, a street address plus a combined suburb, state and postcode line, or a full address as one string. The request holds between 1 and 200 items.

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

Address Validate is the single-address form of this check. Real Estate Search (Bulk) takes the same batch approach for property listing history.

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

All Address endpoints

Questions

Questions we get asked about bulk address validation

Do we need a developer to implement this?

Yes. Address Validate Bulk is a REST endpoint that takes a JSON array of up to 200 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 200 items. Each item holds one address in one of three forms: a street address plus at least one of suburb or postcode, a street address plus a combined suburb, state and postcode line, or a full address as a single string. Each item may also carry a check_id of your choosing.

What comes back for each address?

A valid flag, a score from 0 to 10, the matched address, and a list of the changes made to reach the match. An item that could not be processed carries an error field instead. The check_id from the request is echoed on the result.

Which corrections are made?

The same corrections as Address Validate: spelling of the street or suburb name, the street type, the unit type, an adjacent postcode or suburb, and a street number inside a numbered range. Each is only applied where the street number and street name are valid in the resulting suburb or postcode, and each is listed on the result.

How large a file can we process?

Each request takes up to 200 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