Search place suggestions for agent service-area selection
View all Realty in US Property & Mortgage Data endpoints →Search location information for an agent-discovery workflow using the required input text. The documented default text is cali. Optional area_types controls the location categories: neighborhood, city, county, postal_code, building, and street. Its documented default is the comma-separated string neighborhood,city,county,postal_code,building,street. limit defaults to 10 and has a documented maximum of 20. Treat results as candidates for a user-selected service area rather than automatically choosing a location or sending an agent-list request. No successful probe response is supplied for this endpoint. The unverified source example is truncated and begins with an agents array containing agent-profile information; it does not establish a reliable location-suggestion response schema. Consequently, result field names, identifier formats, coordinates, and an empty-result envelope are not verified. The agent-list contract describes marketing_area_city as a location result id from this endpoint, but that mapping must be checked against an actual response before use. Do not assume identifiers or fields match the property-location autocomplete operation.
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/agents-v2-search-location API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/agents-v2-search-location?key=<API_KEY>&area_types=neighborhood%2Ccity%2Ccounty%2Cpostal_code%2Cbuilding%2Cstreet&input=cali&limit=10'
Query Result
Use Cases
- Build a service-area text picker that searches partial place names and waits for an explicit user selection before preparing an agent-directory query.
- Offer a city-and-county location mode using the documented area_types values while keeping the query text separate from any selected result identifier.
- Design a compact mobile place-selection menu using the default limit of 10 or another value within the documented maximum of 20.
- Test the eventual marketing-area identifier mapping independently from property autocomplete so similarly named places do not silently share incompatible identifiers.
- Handle unmatched or ambiguous place text with a user-facing refinement step rather than assuming a successful response must contain a usable suggestion.
Frequently asked questions
What should I send in input?
Send a location term or phrase. The documented default and example are cali, and California is also described as an example place term. input is required; this endpoint is for locations, not searching agents by their names.
Which area_types values are documented?
The documented categories are neighborhood, city, county, postal_code, building, and street. The default is the comma-separated string neighborhood,city,county,postal_code,building,street. Keep this parameter as a string, not a JSON array.
How many location results can I request?
limit defaults to 10 and has a documented maximum of 20. Although the source describes it as a paging input, this endpoint exposes no offset or page parameter, so a next-page mechanism is not established.
Are the location response fields verified?
No. There is no successful probe response in the supplied evidence. The source example is truncated and starts with agent-profile records rather than a verifiable location-suggestion schema. Do not rely on that example for required suggestion fields or an empty-result shape.
Can a location result be sent directly as marketing_area_city?
The agent-list documentation describes marketing_area_city as an id from this location-search endpoint. However, the returned identifier format has not been verified here. Require a selected result, confirm the actual response mapping, and do not reuse assumptions from property autocomplete. Selecting a suggestion should not itself send an agent search.