AddressFinder API

Name: AddressFinder API API
Brand: AddressFinder API
Availability: InStock

★ Only Publicly Available SpecData EnrichmentAddress ValidationapiKey10 EndpointsREST

For Agents

Search and verify Australian and New Zealand addresses, look up suburbs and postcodes, and verify email addresses. Used by AU/NZ-focused checkout, signup, and CRM hygiene agents.

Quickstart

Get started with AddressFinder API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search australian or new zealand addresses"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AddressFinder API API.

Search Australian addresses with type-ahead matching to power autocomplete fields

Retrieve full metadata for a specific Australian address including DPID and geocode

Search New Zealand addresses with the same autocomplete pattern

Look up suburb and postcode metadata for both AU and NZ locations

GET STARTED

Start building with AddressFinder API API

Explore with Jentic

View OpenAPI Spec

Use for: Search Australian addresses matching '123 collins street' for an autocomplete dropdown, Get the full DPID and geocode for a specific NZ address, Find all suburbs in a Sydney postcode, Verify whether an email address is deliverable

Not supported: Does not validate addresses outside Australia and New Zealand, calculate routes, or render maps — use for AU/NZ address autocomplete, verification, and email checks only.

Jentic publishes the only available OpenAPI specification for AddressFinder API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AddressFinder API, keeping it validated and agent-ready. AddressFinder provides address autocomplete, verification, and metadata lookup tuned specifically for Australian and New Zealand postal addresses, plus an email verification endpoint. Each country has dedicated address search, address-info detail, location (suburb/postcode) search, and location-info endpoints, so agents can drive both type-ahead UX and back-end data quality checks. Authentication uses an API key passed as the key query parameter.

Use Cases

Patterns agents use AddressFinder API API for, with concrete tasks.

★ Address autocomplete on AU/NZ checkout

E-commerce stores shipping to Australia or New Zealand integrate AddressFinder's /au/address and /nz/address endpoints to power type-ahead address fields. As the shopper types, the API returns ranked candidates so the user picks a verified address in two or three keystrokes. This reduces invalid-address shipping errors and shortens checkout time noticeably.

On each keystroke after three characters, GET /au/address with q set to the partial input and return the top five candidates as suggestions.

CRM address hygiene

Sales operations periodically clean their CRM by re-validating customer addresses. For each AU or NZ record, the agent calls /au/address/info or /nz/address/info to confirm the address still maps to a known DPID and to standardise formatting. Records that fail validation are flagged for manual review, while passes are upgraded with the canonical address string and geocode.

For each customer with country AU, GET /au/address/info with the existing address; if it returns a valid DPID, write the canonical formatted_address back to the CRM.

Email verification on signup

Marketing teams want to suppress disposable, mistyped, or undeliverable emails before they reach the email service provider. The /email/v1/verification endpoint returns a deliverability verdict and metadata so signup forms can reject obvious bad inputs and the back-end can defer marketing sends for risky ones. This keeps sender reputation higher and reduces wasted credits.

On signup form submit, GET /email/v1/verification with the entered email and reject the form if the response status is 'undeliverable' or 'invalid'.

AI agent address validation via Jentic

An AI agent in a contact-centre app uses Jentic to validate an Australian address dictated over the phone. The agent searches 'verify australian address', loads the GET /au/address/info schema, fills the address string from the transcript, and confirms the DPID match back to the operator. The AddressFinder API key never enters the agent's context — Jentic adds it from the MAXsystem vault.

Use Jentic to search 'verify an australian address', load the GET /au/address/info schema, and execute with q set to the dictated address.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for addressfinder api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/au/address

Search Australian addresses

GET

/au/address/info

Get detailed Australian address information

GET

/nz/address

Search New Zealand addresses

GET

/nz/address/info

Get detailed New Zealand address information

GET

/au/location

Search Australian locations

GET

/nz/location

Search New Zealand locations

GET

/email/v1/verification

Verify an email address

GET

/au/address

Search Australian addresses

GET

/au/address/info

Get detailed Australian address information

GET

/nz/address

Search New Zealand addresses

GET

/nz/address/info

Get detailed New Zealand address information

GET

/au/location

Search Australian locations

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The AddressFinder API key is stored encrypted in the Jentic MAXsystem vault and appended to the URL's key parameter at execute time. Agents never receive the raw key, even though the API places it on the query string.

Intent-based discovery

Agents search by intent (e.g., 'autocomplete an australian address') and Jentic returns the matching AddressFinder operation with its input schema — important because AddressFinder does not publish a public OpenAPI spec.

Time to first call

Direct integration without a published spec: half a day reading the docs site and validating each parameter. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HERE Maps API

Global geocoding and mapping API covering many more countries than AU/NZ.

Pick HERE when addresses are global rather than AU/NZ-only — it handles every country but is less tuned to local AU/NZ formats.

Alternative

Geocodio API

Address verification and geocoding focused on US and Canadian addresses.

Choose Geocodio when the addresses are North American — it's the regional equivalent of AddressFinder for the US/Canada.

Complementary

Melissa Data API

Global data quality suite covering address, name, email, and phone validation.

Use Melissa when a single workflow needs verification across many data types and AddressFinder's AU/NZ depth is not required.

FAQs

Specific to using AddressFinder API API through Jentic.

Why is there no official OpenAPI spec for AddressFinder API?

AddressFinder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AddressFinder API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AddressFinder API use?

AddressFinder uses an API-key scheme: a key issued in the AddressFinder dashboard is sent as the key query parameter. Jentic keeps the key in the MAXsystem vault and appends it at execute time so it never appears in agent context, even though it travels on the URL.

Can I look up Australian and New Zealand addresses with the same API key?

Yes. The /au/address and /nz/address endpoints share authentication — one key works for both countries. Use /au/address/v2 when v1 returns ambiguous matches and you want the refined ranking.

How do I validate an address through Jentic?

Search Jentic for 'verify australian address' or 'verify new zealand address', load the GET /au/address/info or /nz/address/info schema, and execute with q set to the address string. The response includes the DPID, formatted address, and geocode.

Are there rate limits on the AddressFinder API?

AddressFinder applies per-account credit and rate limits scaled to plan; the spec does not declare a fixed RPS value. When 429 responses occur Jentic surfaces them so retry logic can read the Retry-After header.

Does this API support countries other than Australia and New Zealand?

No. The address-related endpoints are scoped to AU and NZ datasets only. For US, UK, or global address validation, use a competing provider such as Smarty, Loqate, or HERE.