Look up location filter values
Search the location vocabulary for the exact values a location filter will match.
Location filters are matched against a fixed vocabulary of place names, spelled the way the underlying data spells them. A value outside that vocabulary matches no contacts, and because search returns 200 with an empty data array either way, a misspelling is indistinguishable from a genuinely empty market. This endpoint is how you tell the two apart: look a place up, then send the returned location string verbatim.
The vocabulary is too large to enumerate — roughly 170,000 cities and 727,000 postal codes — so there is no full list to download. Query it instead. Results are ordered by contact volume, so the first result is usually the place you meant.
US state names and abbreviations, and the country aliases US, USA and United States of America, are resolved by the location filters directly and need no lookup.
This endpoint consumes no search credits.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Query Parameters
A partial place name, matched at the start of any word — york finds New York. Search one place name at a time rather than a whole comma-separated tag.
"austin"
Maximum results to return, 1-100.
1 <= x <= 100Restrict results to these tiers of the vocabulary. Repeat the parameter or pass a comma-separated list. Omit for all tiers.
Use state-country or country to find a value for contactState / companyState or contactCountry / companyCountry, city-state-country for a free-form locations tag, and postcode for contactZipCode / companyZipCode.
city-state-country, state-country, city-country, country, postcode Response
Matching locations, most common first
Matching locations, ordered by contact volume. An empty array means the vocabulary holds nothing resembling the query.
