▣ GEOLOCATION

Address Validation & Location Lookup API

What it does

Address Validation checks a postal address from either query parameters or a JSON body and returns a simple validation envelope with success and code.

Send an address as street, address, city, state, country, or postcode, depending on what you have available. The GET endpoint accepts those fields as query parameters; the POST endpoint accepts the same address parts inside body. The response is an object with a numeric code, a boolean success, and additional module blocks.

Use Address Validation when you need to confirm user-entered shipping addresses before checkout, clean up address data before storing it, or gate downstream workflows on a basic validity check. It fits forms, customer onboarding, and logistics systems where you want a fast pass/fail result without parsing a larger geocoding payload.

▣ ENDPOINT 01 / 02

GET

Address Validation

https://api.eu.apyhub.com/quadlem/address-validation/address-validate

QUICKSTART

GUIDE

Quickstart

Use the following request to validate an address and retrieve the closest matching location along with confidence and risk information.

curl -X GET "https://api.eu.apyhub.com/quadlem/address-validation/address-validate?address=1600+Pennsylvania+Ave+NW&city=Washington&state=DC&country=US&postcode=20500" \
  -H "apy-token: $APY_TOKEN"

What you'll get back

A successful request returns the validation result, confidence score, resolved address details, geographic coordinates, and a breakdown of which address components matched.

{
  "success": true,
  "code": 200,
  "valid": true,
  "status": "close",
  "confidence": 73,
  "risk_score": 0.05,
  "resolved": {
    "label": "Example City, Example State, 141001, India",
    "city": "Example City",
    "state": "Example State",
    "postcode": "141001",
    "country": "India",
    "lat": 30.9090157,
    "lng": 75.851601
  },
  "matches": {
    "house_number": false,
    "road": false,
    "city": true,
    "state": true,
    "postcode": false,
    "country": false
  }
}

Note: This example shows a partial, typo-tolerant match. The full response also includes additional metadata such as input, disclaimer, model_version, and request_id.

TRY ITLIVE · 50 ATOMS

API key

Loading your default key…

The full key is used to call the gateway and stays in this tab — never sent to orbit or saved.

About this endpoint

What it does

Validates a postal address from query parameters using OpenStreetMap/Nominatim data. Typo-tolerant and fuzzy: unmatched or missing fields (e.g. a partial street) don't sink the lookup — the query is progressively relaxed and matched at the city/state/country level where a precise match isn't possible. Returns a match status, confidence score, resolved address, coordinates, and per-field match flags.

Query Parameter(s)

Attribute	Type	Mandatory	Description
address	String	No	Free-text address (preferred).
street	String	No	Street address line.
city	String	No	City name.
state	String	No	State or region.
postcode	String	No	Postal or ZIP code.
country	String	No	Country name or code.

Response

Returns a JSON object with the overall match verdict, a confidence and risk score, and the resolved address alongside per-field flags showing which submitted components matched.

Attribute	Type	Description
success	Boolean	Whether the request succeeded.
code	Integer	Numeric response code.
geocoder_ok	Boolean	Whether the underlying geocoder responded successfully.
valid	Boolean	Whether a usable address match was found.
status	String	Match quality — `exact`, `close`, `partial`, or `not_found`.
confidence	Number	Match confidence (0–100).
risk_score	Number	Address-related fraud risk score.
input	Object	The submitted fields plus the constructed search query.
resolved	Object	The best-matched address — label, components, coordinates, and OSM reference.
matches	Object	Per-field boolean flags showing which submitted components matched the resolved address.
disclaimer	String	Notes that this is OSM/Nominatim-based, not postal-authority (CASS) certified.
model_version	String	Address validation model version.
request_id	String	Unique identifier for this request.

▣ ENDPOINT 02 / 02

POST

Address Validation

https://api.eu.apyhub.com/quadlem/address-validation

QUICKSTART

GUIDE

Quickstart

Use the following request to validate an address by submitting structured address fields in the request body and retrieve the closest matching location.

curl -X POST "https://api.eu.apyhub.com/quadlem/address-validation" \
  -H "apy-token: $APY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "city": "Washington",
    "state": "DC",
    "street": "1600 Pennsylvania Avenue NW",
    "address": "1600 Pennsylvania Avenue NW, Washington DC",
    "country": "US",
    "postcode": "20500"
  }'

What you'll get back

A successful request returns the validation result, confidence score, resolved address details, geographic coordinates, and a breakdown of which address components matched.

{
  "success": true,
  "code": 200,
  "valid": true,
  "status": "close",
  "confidence": 73,
  "risk_score": 0.05,
  "resolved": {
    "label": "Example City, Example Tahsil, Example City, Example State, 141001, India",
    "city": "Example City",
    "state": "Example State",
    "postcode": "141001",
    "country": "India",
    "lat": 30.9090157,
    "lng": 75.851601
  },
  "matches": {
    "house_number": false,
    "road": false,
    "city": true,
    "state": true,
    "postcode": false,
    "country": true
  }
}

Note: This example demonstrates a partial, typo-tolerant match. The full response also includes additional metadata such as input, disclaimer, model_version, and request_id.

TRY ITLIVE · 50 ATOMS

API key

Loading your default key…

The full key is used to call the gateway and stays in this tab — never sent to orbit or saved.

About this endpoint

What it does

Validates a postal address submitted as fields in a JSON body, using OpenStreetMap/Nominatim data. Same behavior as the GET variant — typo-tolerant and fuzzy, with the query progressively relaxed so missing or unmatched fields (street, postcode, etc.) don't sink the lookup. Returns a match status, confidence score, resolved address, coordinates, and per-field match flags.

Request Body

Parameter	Type	Mandatory	Description
address	String	No	Free-text address (preferred).
street	String	No	Street address line.
city	String	No	City name.
state	String	No	State or region.
postcode	String	No	Postal or ZIP code.
country	String	No	Country name or code.

Response

Returns a JSON object with the overall match verdict, a confidence and risk score, and the resolved address alongside per-field flags showing which submitted components matched.

Attribute	Type	Description
success	Boolean	Whether the request succeeded.
code	Integer	Numeric response code.
geocoder_ok	Boolean	Whether the underlying geocoder responded successfully.
valid	Boolean	Whether a usable address match was found.
status	String	Match quality — `exact`, `close`, `partial`, or `not_found`.
confidence	Number	Match confidence (0–100).
risk_score	Number	Address-related fraud risk score.
input	Object	The submitted fields plus the constructed search query.
resolved	Object	The best-matched address — label, components, coordinates, and OSM reference.
matches	Object	Per-field boolean flags showing which submitted components matched the resolved address.
disclaimer	String	Notes that this is OSM/Nominatim-based, not postal-authority (CASS) certified.
model_version	String	Address validation model version.
request_id	String	Unique identifier for this request.

▣ COMMON ERRORS

Errors any endpoint can return

400bad_request

Required parameter missing or malformed body.

401unauthorized

API key missing, revoked, or not authorized for this service.

429rate_limited

Your plan's per-second rate exceeded. Retry with exponential backoff.

503upstream_busy

Backend temporarily unavailable. Try again in a few seconds.

Similar APIs

Closest matches in the catalog based on this service.

CALLValidate UK Postcodes APIApyHub CALLIP Address Lookup APIQuadlem, LLC CALLSearch US Address APIDosvak LLC CALLValidate Indian Postcodes APIApyHub

From the blog

Reads that touch this API.

Email Validation API: How It Works + 7 Options ComparedSep 24, 2026 Step-by-Step Guide to Sending Emails Programmatically with APIs using GoAug 7, 2026 Data Validation APIs: What Your Checks Actually ProveSep 8, 2026 The Importance of Email Validation for Data AccuracyAug 7, 2026