Realtor Agent Location Autocomplete API

Submit query text with optional limit to evaluate the documented agent-location autocomplete route. Its suggestions are intended for selecting the location input used by agents-list; inspect the actual returned identifier before forwarding it. This route was not live-tested, so suggestion field names, empty-result behavior and limit enforcement are unconfirmed. Keep its location values distinct from property-auto-complete IDs and finance-tool locations rather than assuming those formats are interchangeable.

API Features

Agent-directory location query query is the text entry point for this dedicated agent-search suggestion route.

Agent-search handoff evaluation Inspect actual suggestion identifiers before passing a selected value into agents-list.

Documented agent suggestion count limit is optional; its effect and no-match behavior were not observed for this route.

Agent location namespace separation Do not assume agent suggestions use the same IDs as property searches or financial tools.

Live API Demo

GET /api/project/realtor/agents-auto-complete

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/realtor/agents-auto-complete?key=<API_KEY>&query=new+york'

curl -X GET 'https://api.opendata-api.com/api/project/realtor/agents-auto-complete?key=<API_KEY>&query=new+york'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Build an agent-directory area picker after verifying its actual suggestions and identifiers.
Disambiguate similarly named service locations before saving an agent search.
Test agent suggestion-count behavior before setting a UI display limit.
Validate the autocomplete-to-agents-list location handoff independently of property search.

Frequently asked questions

Can I reuse city IDs from property autocomplete?

Do not assume compatibility. Agent-directory, property-search and financing locations have separate input contracts. Validate actual returned values and downstream acceptance.

Which suggestion field should be passed to agents-list?

The actual identifier field was not live-confirmed. Inspect this suggestion response and check the agents-list id input instead of guessing a path from the operation name.

How should empty suggestions or ignored limits be displayed?

Validate this operation no-match and count behavior first, then design an empty state and local display cap. Do not assume the tested property-autocomplete response structure applies here.

Related operations

Guides

View Subscription Plans →

Find Locations for Agent Search