Reverse Address API
Reverse Address API
Reverse Address API validates and normalizes input addresses while providing comprehensive insights into current residents’ information, including demographics, historical addresses, relatives and associated people.
Reverse Address 3.1
Query Parameters
The first line of the street part in the structured address. Cannot be longer than 1000 characters. Example:
street_line_1=100 Syrws StThe second line of the street part in the structured address. Cannot be longer than 1000 characters. Example:
street_line_2=Ste 1The name of the city in the structured address. Cannot be longer than 500 characters. Example:
city=SeattleThe state code of the structured address. Cannot be longer than 100 characters. Example:
state_code=WAThe postal code of the structured address. Cannot be longer than 100 characters. Example:
postal_code=98101The ISO-3166 alpha-2 country code of the address. Cannot be longer than 100 characters. Example:
country_code=USHeaders
Your API key for authentication. Example:
{{ apiKey }}Response
The persistent ID of the address.
True if the address is valid.
The first line of the street part in the structured address.
The second line of the street part in the structured address.
The name of the city in the structured address.
The postal code of the structured address.
The state code of the structured address.
The ZIP+4 code of the structured address (USA).
The ISO-3166 alpha-2 country code of the address.
The coordinates of the geographical location of the address.
True if the address is currently receiving mail.
True if the address is a business address.
The type of the delivery point of the address. Enum: SingleUnit MultiUnit POBox PartialAddress
The list of current person and business residents at the address.
Error details in case of an error.
Warnings returned as part of the response, if applicable.
Enum: Invalid Address Missing Input Invalid house/building number Missing unit/apt/suite number Invalid unit/apt/suite number
Enum: Invalid Address Missing Input Invalid house/building number Missing unit/apt/suite number Invalid unit/apt/suite number
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.
