Address Validation API
Address Validation API
Address Validation API validates and normalizes US addresses, and provides valuable insights like latitude and longitude coordinates.
Address Validation API 3.0
Query Parameters
The first line of the street part in the structured address. Example:
street_line_1=800 Bellevue Way NEThe second line of the street part in the structured address (e.g. apartment or suite number). Example:
street_line_2=Ste 100The name of the city in the structured address. Example:
city=BellevueThe state code of the structured address. Example:
state_code=WAThe postal code of the structured address. Example:
postal_code=98004Headers
Your API key for authentication. Example:
{{ apiKey }}Response
The persistent ID of the validated address. Format:
Location.<uuid>. Only present when the address is valid.True if the address is valid.
The first line of the street part in the structured address, normalized by USPS CASS standards.
The second line of the street part in the structured address. Returns
null for this API — unit information is incorporated into street_line_1 during normalization.The name of the city in the structured address.
The 5-digit postal code of the structured address.
The 4-digit ZIP+4 extension of the structured address (USA).
The state code of the structured address.
The ISO-3166 alpha-2 country code of the address. Always
US for valid responses from this API.The coordinates of the geographical location of the address. Only present when CASS returns coordinate data.
An error message string if a partial error occurred during processing, otherwise
null.Warnings returned as part of the response, if applicable.Enum: Missing Input Invalid address Invalid house/building number Missing unit/apt/suite number Invalid unit/apt/suite number Non-US country address validation is not supported. Address validation could not be completed at this time. Please try again later
Error Responses
400 Bad Request
The server cannot process the request due to client-side errors.Check for: Syntax errors in the request script, malformed JSON, or invalid parameters.403 Forbidden
The request is understood, but the server is refusing to fulfill it.- Invalid API Key: The key is incorrect or deactivated. Check for: Trailing spaces, syntax errors, or incorrect character counts.
- API Key Missing: The request header did not include an API key.
- API Key Disabled (Portal Issue): The key is inactive. Check for: Insufficient funds in your self-serve wallet or if a Trestle Admin manually deactivated your API key.
- API Key does not have Product Access (Portal Issue): The API key is active, but it is not enabled for this product or API version. Check for: Incorrect endpoint, incorrect API version, or missing product access on the key.
- API Key Expired: The key has reached its end-of-life (primarily affects Trial users).
429 Too Many Requests
You have sent too many requests in a given amount of time.- Rate Limit Exceeded: You have surpassed the queries-per-second (QPS) threshold for your tier.
- Quota Exceeded (Portal Issue): You have reached the total volume allowed for your current billing cycle. Upgrade your plan in the portal to resume service.
