Skip to main content

Address Validation

Validate an Address

In this guide, we will validate and standardize an address against the address standardization service.

Overview​

Address validation standardizes an address against the address standardization service and confirms that it resolves to a real, known location. Running this check before creating a premises monitorable helps you catch typos and unmatched addresses early, so you only monitor locations that the platform can recognize.

Getting Started​

This endpoint uses partner authentication, so you need a partner access token (not an application token).

  1. Log in to the Partners Portal
  2. Use the Set Access Token button in the navbar to configure your partner access token

Once your partner access token is configured, it is automatically included in the Authorization header for the request below.

Validate an Address​

To validate an address, send a POST request to the /addresses/validate endpoint with the address details:

Request body

Primary street address line

Secondary address line such as unit or suite

City name

State or subdivision code

Postal or ZIP code

Country code

County name

Latitude of the address

Longitude of the address

cURL command

cURLPOST
curl -X POST "/v1/addresses/validate" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -d '{
  "addressLine1": "1501 Yamato Rd",
  "city": "Boca Raton",
  "state": "FL",
  "postalCode": "33431",
  "country": "US"
}'

💡 Set your access token in the navbar to auto-fill the Authorization header

Request Fields​

The following fields are required:

  • addressLine1 - Primary street address line (e.g., 1501 Yamato Rd)
  • city - City name (e.g., Boca Raton)
  • state - State or subdivision code (e.g., FL)
  • postalCode - Postal or ZIP code (e.g., 33431)
  • country - Country code (e.g., US)

The following fields are optional:

  • addressLine2 - Secondary address line such as unit or suite (e.g., Suite 200)
  • county - County name (e.g., Palm Beach)
  • latitude - Latitude of the address (e.g., 26.3989)
  • longitude - Longitude of the address (e.g., -80.1003)

Response​

The response contains a single valid field:

{
  "valid": true
}

valid is true only when the standardization service returns a successful result and matches the address to a known location. It is false when the address cannot be matched.

A valid: false result means the address could not be matched. Correct the address before using it to create a monitorable.

Conclusion​

You've successfully validated an address. Use this check to confirm an address resolves before creating a premises monitorable.

Learn More​

API Reference​