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
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-list-deprecated 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>'
Query Result
Use Cases
- Inventory the exact ZIP code, name and entity-type filters used by an older local agent directory before replacing its search screen.
- Build a migration checklist that flags buyer/seller role, price, rating or recommendation filters without a documented current equivalent instead of silently broadening results.
- Compare stored limit, offset and sort settings with a proposed directory replacement to expose paging and ordering differences before a cutover.
- Review whether an existing office or team search incorrectly treats types and agent_type as the same control, preserving their distinct documented purposes.
- Prepare legacy directory fixtures that handle an empty object without inventing an agent list, total count or populated advertiser_id field.
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.