Legacy agent listing lookup (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Retrieve the legacy listing selection associated with an agent. This deprecated operation is intended for maintaining and auditing existing agent pages, not for new integrations. Supply all three required query parameters from the same legacy /agents/list result: numeric agent_id from member/id, numeric fulfillment_id from advertiser_id, and string id from abbreviation. Optional page selects a page; optional type selects all, forSale, forSold, forRent, or openHouses. The documented examples use page=1 and type=all, but no omitted-value behavior or page size is established. The available response documentation contains only an unverified HTTP 200 example of an empty JSON object ({}). No probe response is available, and no listing fields, result count, pagination envelope, or error schema are documented for this route. Do not interpret that example as verified empty inventory or proof that this deprecated operation remains available. Compare identifier requirements and response structure with the current agent-listing contract before migrating saved pages; identifiers must not be assumed interchangeable.
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-get-listings-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/agents-get-listings-deprecated?key=<API_KEY>&agent_id=<agent_id>&fulfillment_id=<fulfillment_id>&id=<id>'
Query Result
Use Cases
- Inventory saved agent-listing pages that depend on the original agent_id, fulfillment_id, and abbreviation combination.
- Record the page and type selections used by older for-sale, sold, rental, and open-house tabs before redesigning their navigation.
- Build a manually verified migration test set for comparing the deprecated listing lookup with the current agent-listing contract.
- Review cached legacy inventory displays so an undocumented empty-object example is not mistaken for evidence of zero available properties.
Frequently asked questions
Which identifiers are required for the legacy agent listing lookup?
All three are required: numeric agent_id, numeric fulfillment_id, and string id. The legacy /agents/list documentation maps them respectively to member/id, advertiser_id, and abbreviation. Keep the values associated with the same agent result rather than deriving one from another.
Which listing types does the type parameter document?
The documented values are all, forSale, forSold, forRent, and openHouses. The parameter is optional and the example uses all, but the supplied evidence does not confirm what happens when it is omitted or whether each category remains available.
How is pagination specified for this deprecated route?
The optional numeric page parameter selects a page, with 1 shown as the example. The documentation does not establish a page size, page limit, total-count field, or response pagination envelope.
What listing fields can I rely on in the response?
None are established by the supplied evidence. The only documented example is labeled HTTP 200 and contains {} without any listing fields. It is unverified, no probe response is available, and the example must not be treated as verified empty inventory.
Should a new agent inventory page use this operation?
No. It is a deprecated migration surface for existing integrations. Review the current agent-listing contract and verify identifier mappings and response fields before moving a saved page; this route does not provide automatic conversion or fallback.