Skip to main content

Addressfinder frequently asked questions

General Addressfinder frequently asked questions below. We also have specific FAQs for each integration and you can use search to quickly find what you are after.

Technical

How should I test the service?

We recommend testing the service by searching a variety of addresses, emails or phone numbers and checking that the correct data populates your fields accurately.

Is Addressfinder compatible with jQuery?

Yes. Addressfinder will work with JQuery or any other JavaScript framework. We have purposely built Addressfinder to be non-conflicting with all JavaScript libraries.

What browsers is the widget compatible with?

The Addressfinder widget is compatible with the majority of the latest browsers including: Chrome, Safari, Firefox, Edge and Internet Explore 6 to current.

The widget also works on the latest versions of Opera and Yandex but we do not actively support these browsers.

The Addressfinder Widget is compatible with most screen readers.

Does Addressfinder work with mobile phone applications?

Yes. One of the many features of Addressfinder is its low latency. We have worked hard to make the service as snappy as possible, including ensuring it is hosted in New Zealand to minimise network latency for Australian and New Zealand users. Low latency also helps when Addressfinder is used in mobile applications.

In addition, the Addressfinder Address Autocomplete Widget is very efficient and works well in a mobile context. We have implemented Addressfinder successfully on a number of mobile apps and websites. Generally the data returned by Addressfinder is quite small, so goes well over higher latency mobile networks.

Can Addressfinder handle my busy website?

Our current system architecture has been load tested to handle in excess of 10,000 requests per minute. Our system architecture scales horizontally, and we add additional server instances into our cluster as required.

Are you expecting to exceed several thousand requests per minute on launch? If so, we would appreciate advance notice as this will allow us to add additional server instances in advance of this event.

Can I write my own autocomplete service?

Yes. You will need to follow extra guidelines on top of using the Addressfinder API. Find these steps here.


The widget code generator was created to save you time and effort. We recommend developers use these to provide autocomplete to users.

What content security policy does Addressfinder require?

The Addressfinder widget requires permission from your content security policy (CSP) to:

  • Load our widget.js file
  • Make outgoing requests to the Addressfinder API
  • Load our stylesheet file

Our API and related assets are hosted on api.addressfinder.io.

We recommend the following values be added in your content security policy:

script-src https://api.addressfinder.io;
connect-src https://api.addressfinder.io;
style-src https://api.addressfinder.io;

Data

Where does the address information come from?

The Australia address data comes from three main sources: The Australia Post PAF (Postal Address File), G-NAF address database, the Australian Bureau of Statistics and augmented by Addressfinder database.


The New Zealand data comes from four main sources: The New Zealand Post PAF (Postal Address File), LINZ AIMS, Stats NZ, Open Street Maps and augmented by Addressfinder database.


The international address data comes from ESRI and HERE for addresses located in regions not covered by our regional datasets.


More details on these data sources and the associated AU, NZ and Int metadata available.

Are all possible Australian addresses listed in the Addressfinder database?

Pretty much. Addressfinder is Australia's most comprehensive address database with over 212 million official and alias addresses.

Updating monthly, we work with our data partners to ensure the database is as up to date as possible.


How often do you update your address databases?

Monthly. Both the Australian and New Zealand address databases are updated on a monthly basis.

Why do some addresses not appear in Addressfinder's database?

Here are some reasons why you might not be able to find an address with Addressfinder:

  • Custom filters - integration setting preventing certain addresses ie. PO Boxes.
  • New addresses - can take time to make it through authoritative data sources.
  • "Grey" addresses - addresses that have been used for a long time but not offical.

Read the detailed breakdown of these reasons

What happens when an address isn't in the database?

When a user enters an address that is not listed in the database, they will still be able to enter the address details manually. Addressfinder will still return addresses that are the closest matches to the address that has been entered, but if the correct address is not listed the user can complete the Address Line 1 entry, and then move on to 'Address Line 2, Suburb, Post Code etc'. Therefore you will not lose customers because their address is not available for selection from the drop down menu.

What is the difference between canonical and alias addresses?

Canonical addresses are the official addresses supplied to us by authoritative sources ie. Australia Post. The widget always selects this address by default.


Alias Addresses have unofficial address components including nearby suburbs or commonly misspelled street names. They are included in the database for ease of address selection. The default action of the widget is to take the alias and return the (corrected) canonical address.


The Addressfinder APIs will return both an id and a canonical_address_id.

Read the detailed breakdown of canoncial v alias addresses.

What's the difference between 'city' and 'mailtown' in New Zealand?

City is the physical town or city as named by LINZ. Mailtown is the town associated with the NZ Post delivery point.

If you would like to limit your search to addresses that are deliverable by NZ Post, you can collect only postal addresses.

Does every address record in Addressfinder have a DPID?

No, not every record in Addressfinder has a DPID. Only those addresses that have a "delivery point" are assigned an ID. These DPID fields come from the New Zealand Post PAF database. They identify those addresses that can have mail delivered by a postie.


As a result, some of your address records might not have a DPID against them. NZ Post typically do not deliver to addresses in the CBD of major cities, or to many rural destinations.


Within our system these addresses are sourced from Land Information New Zealand. The unique identifier for LINZ addresses is the aims_address_id field.


You can find out more about the various fields returned from Addressfinder in our API documentation

Address services

How can I disable the browser autofill?

Disabling the browser autofill is often a good idea as the autofilled addresses may contain errors and won't align with your config needs. Read our steps to do this.

How do I get NZ Post deliverable addresses?

It is possible to limit your search to postal addresses only, if your objective is to collect only addresses that NZ Post deliver to.


This is achieved by passing 'delivered:1' to the Address Autocomplete API or configuring in the widget constructor.


This parameter is accessible from the JavaScript widget using the address_params option.

What data is returned from the Address Verification API and Bulk service?

The data returned when verifying Australian Addresses is different to New Zealand address. In addition to the country, the dataset you are verifying addresses against also have an impact.

Why do some addresses change when selected by the user?

Some addresses change when they are selected because the selected address is an alias address and it is replaced with the correct canonical address. 


Alias addresses contain unofficial or inaccurate address components. They are displayed in the search results, in order to better enable customers to find their address, once selected they are replaced with the correct, canonical address.


Read more on conanical and alias addresses

Email services

What are the default rules that are applied to the email verification widget?

In the absence of rules being specified in the widget code, the following rules will be applied by default:

AttributeDefault rule
disposableblock
roleallow
publicallow
unverifiedblock
What are the default messages that are displayed by the email verification widget?

In the absence of messages being specified in the widget code, the following default messages will be displayed if the response triggers one of the rules (default or supplied):

ResponseDefault warn messageDefault block message
disposable"This is a disposable email address.""Disposable email addresses are not permitted."
role"This is a group email address.""Group email addresses are not permitted."
public"This is a public email address.""Public email addresses are not permitted."
unverified"This email address could not be verified. Check spelling and retry.""This email address could not be verified. Check spelling and retry."
What is a disposable email address?

Disposable email addresses are addresses that can be created with little effort, used for a fixed period of time, and then deleted. Examples of disposable email addresses include:

  • Hide My Email - from Apple and other premium providers
  • Throw-away email solutions - such as Mailinator or 10 Minute Mail ie.x9oxd2d@tmpnator.live

Addressfinders email service can be configured to block disposable email addresses which we generally recommend.

Alternatively configure to warn with custom message.


Find out more about email disposable email addresses

What is a catch all email domain?

A catch all domain, also known as ‘accept-all’ or ‘wild-card’, refers to a mail server that is configured to accept all emails sent to the domain regardless of the email account provided.


If the provided email account exists, emails sent to it will be delivered to that inbox. If the provided email account does not exist, emails sent to it will be delivered to a separate inbox that may or may not be monitored.

Phone services

What are the default rules applied by the Phone Verification widget?

In the absence of rules being specified in the widget code, the following default rules will be applied:


AttributeDefault rule
unverifiedblock
countryNotAllowedblock
nonMobileallow
What are the default messages displayed by the Phone Verification widget?

In the absence of custom messaging being supplied in the widget code, the following default messages will be returned when the response matches the rules (supplied or default):


ResponseDefault warn messageDefault block message
unverified"Phone number not verified.""Phone number not verified."
countryNotAllowed"Preferred countries: {LIST}""Allowed countries: {LIST}"
nonMobile"Mobile phone numbers preferred.""Mobile phone numbers required."
What are all of the possible responses returned in the not_verified_code field of the Phone Verification API response?
  • LINE_DISCONNECTED
  • COUNTRY_NOT_ALLOWED
  • COUNTRY_NOT_SUPPORTED
  • LINE_TYPE_MUST_BE_MOBILE
  • INVALID_FORMAT
What are all possible responses returned in the line_status field of the Phone Verification API response?
  • connected
  • disconnected
  • indeterminate
What are all possible responses that may be returned in the line_type field of the Phone Verification API response?

ResponseDescription
fixed_lineA landline phone number. Not expected to be able to receive SMS messages.
mobileA phone number associated with a mobile/cellular phone.
pagerA phone number associated with a pager device.
fixed_or_mobileA phone number associated with either a fixed or mobile device.
toll_freeA toll-free phone number.
shared_costA shared cost phone number.
premium_rateA premium rate phone number.
voipA virtual phone number.
personal_numberA phone number designated for personal use.
uanA universal access number, which can route incoming calls to different destinations.
voicemailA phone number that is associated with a voicemail service.

Note: Not all of these line types are returned for every country.

Account and Plans

What is a lookup?

A ‘lookup’ is the term we use to measure the activity of your Addressfinder account.

One lookup is counted every time you or a user collects address metadata. This could happen when a user selects a verified address from the widget dropdown, or when you make a direct call to the Metadata API. The searching and display of addresses is not charged.


One lookup is also counted when an address verification call is made and Addressfinder considers the address to be valid. Invalid email addresses are not charged.


Lastly, one lookup is counted when using the address verification API, either via the portal or direct API. Only verified addresses are charged as a lookup.

What happens if I run out of lookups?

Monthly plan - If you use up 100% of your lookups while on a paid monthly plan, the Addressfinder service will continue. The extra lookups you use will be counted and you will be charged for these at the end of the month.

Annual plan - If you run out of lookups on an annual plan, your plan will automatically renew and start a new 12 month term.


You’ll know the roll-over’s coming because you will have received emails sent when you reached 80% and 95% of your plan’s limit. If you receive these emails very early in your plan's term you may wish to consider upgrading to a larger plan as this is likely to be more economical.

What are 'extra lookups' and how are they charged?

Monthly plans only - extra Lookups are the additional lookups or used on top of the prepaid lookups associated with your plan.


These extra lookups or overage charged at the same rate as your plan and is billed at the end of the month when your plan renews.


Annual plans do not have 'extra lookups'. When your plan runs out of lookups it will automatically renew early.


More on billing

Can I change my plan whenever I like?

Yes. Change your plan when it suits you - for example, if your usage changes, or your organisation's financial needs change.

When will my plan change take effect?

The type of change you make will determine when the change takes place:


Change TypeWhen the change will take effect
Free trial to PaidImmediately
Upgrade MonthlyImmediately
Upgrade AnnualAt the end of the current term*
Downgrade MonthlyAt the end of the current month
Downgrade AnnualAt the end of the current term*

*Annual plans will change early if you consume all your lookups.

Do you provide a developer account?

Yes. At our discretion we may provide you with a developer account. The developer account is specifically for development/digital agencies who add the Addressfinder service into multiple clients' systems.


The developer account has the following rules:

  • One developer account per agency.
  • For development purposes only.
  • Addressfinder staff are authorised to invite others from your agency to use the developer account.
  • When the integration is ready for production, the client is to create their own Addressfinder account and the credentials from this account used on an ongoing basis.

If you believe you qualify for a developer account, get in touch with us at support@addressfinder.com.au and we will create the account for you.

I'm a developer, how do I set up a client account?

If you are a developer who is integrating Addressfinder into one client's system, utilise the free trial account for development. This account can then be passed over to the client once development is complete, or the client can use their own account and switch keys.

Can't find what you are looking for?

Get in touch