Legacy city and address autocomplete (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Retained for existing integrations that submit one required input query string to obtain location suggestions. The documented input covers city, district and place names; the endpoint description also mentions street names and address-to-property-identifier lookup. The example input is new york. This deprecated route is a migration surface, not the recommended choice for a new location picker; evaluate /locations/v2/auto-complete instead. The supplied documentation example contains an autocomplete array. Example candidates include _id as a candidate identity, _score as a relevance value, area_type as a location category, centroid.lat and centroid.lon as coordinates, and city, state_code and country as geography. Example counties entries contain fips, name and state_code. Other type-dependent example fields include geo_id, slug_id, county_needed_for_uniq, city_slug_id, line, postal_code, has_catchment, school and school_id. Do not treat these fields as present on every suggestion or confuse a city identity with a property identifier. No successful response from this deprecated route was recorded in the supplied checks. The fields above come from an unverified, truncated documentation example rather than an observed response. Address-to-property resolution is a documented purpose, not a guarantee that a particular address will yield a property identifier. Before migrating, validate suggestion types, optional fields and the inputs accepted by the next property endpoint; do not assume the replacement route has an identical response contract.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/realty-in-us/locations-auto-complete-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/locations-auto-complete-deprecated?key=<API_KEY>&input=<input>'
Query Result
Use Cases
- Inventory older property-search forms that send only input and record how each form handles city, district and address suggestions.
- Create parser fixtures from the legacy documentation example, marking its optional geographic fields as unverified rather than production guarantees.
- Audit whether an existing address workflow incorrectly passes a city candidate identity into a property-detail lookup.
- Plan a location-route migration with explicit tests for candidate categories and missing fields before replacing the deprecated request.
Frequently asked questions
Should a new location picker use this deprecated route?
No. Keep this documentation for existing /locations/auto-complete integrations and evaluate /locations/v2/auto-complete for new work. Validate the replacement response and parameter contract rather than assuming a drop-in substitution.
Which query parameters belong to this legacy endpoint?
The supplied contract exposes only the required string parameter input, with new york as its example. It does not document a limit parameter for this route.
Does entering an address guarantee a property identifier?
No. Address-to-property-identifier lookup is mentioned in the endpoint description, but this route has no recorded successful check in the supplied evidence. A location candidate identity must not automatically be treated as a property identifier.
Are the documented autocomplete fields verified on this route?
No. Fields such as _id, area_type, centroid, city, state_code and counties appear in a truncated documentation example only. Treat them as migration clues, handle absent type-dependent fields and verify the contract before relying on them.