Search the legacy agent directory by ZIP code (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Search the deprecated GET /agents/list directory with a required postal_code and optional filters for name, buyer or seller agent role, result type, minimum rating, minimum recommendations and price bounds. Documented result types are agent, team and office. Pagination uses limit, documented with a maximum of 20, and offset, the number of entries to skip. The sort input supports five documented orderings covering recent activity, recent sales, for-sale count, recommendation count and rating. The available HTTP 200 source example is an empty JSON object; it establishes no agent collection, record fields, total count or pagination metadata. The legacy review operation documents advertiser_id as originating here, but no populated directory record was captured to verify that handoff. This operation was not live-tested. Use it to audit or migrate older directory filters, not as a recommended new integration; do not assume a current search operation has equivalent filter semantics.

API Features

ZIP-scoped legacy directory search Require postal_code while optionally narrowing the directory by an agent, team or company name. Result types are separately selected with types.
Buyer and seller role selection Use agent_type for the documented buyer or seller role and types for agent, team or office entities; these inputs represent different filters.
Rating and recommendation thresholds Express legacy minimum-rating and minimum-recommendation filters using agent_rating_min and recommendations_count_min. Their documented maxima are 5 and 10 respectively.
Legacy price-range filter audit Retain the optional price_min and price_max inputs when reviewing an older integration. The documentation does not specify the transaction or listing price field used by these filters.
Five directory sort modes with offsets Choose among documented activity, sales, for-sale count, recommendations or rating orderings, and retain limit/offset paging with a documented page-size maximum of 20.

Live API Demo

GET /api/project/realty-in-us/agents-list-deprecated

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/agents-list-deprecated?key=<API_KEY>&postal_code=<postal_code>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Is postal_code required even when I search by name?

Yes. postal_code is the required string query parameter. name is optional and is documented for searching an agent, team or company; it does not replace the postal-code requirement.

How do types and agent_type differ?

types selects the documented result entity: agent, team or office. agent_type selects buyer or seller, or can be omitted. These filters are separate and should not be combined into one field.

What are the documented paging and threshold limits?

limit has a documented maximum of 20, and offset is the number of entries to skip. The documented maximum for agent_rating_min is 5 and for recommendations_count_min is 10. No response total or next-page field is established by the empty example.

Which sort values are documented?

The documented values are recent_activity_high, recently_sold_high, for_sale_count_high, recommendations_count_high and agent_rating_high. The supplied sort example is recent_activity_high; it is not evidence of a server default.

What do the price filters and response records guarantee?

price_min and price_max are optional numeric filters, but the documentation does not identify the specific price field they use. The source success example is {}, so record fields, counts and populated advertiser identifiers remain unverified. No live response was captured.

Can I move every legacy filter directly to a current agent search?

Do not assume so. This operation is deprecated. Compare the documented current contract filter by filter and surface unsupported legacy criteria rather than silently dropping them or claiming equivalent results.

Related operations

Guides

View Subscription Plans →