Legacy agent recommendations lookup (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Retrieve the legacy recommendation resource associated with an agent's advertiser identifier. This deprecated operation is a maintenance and migration reference for existing recommendation widgets, not a recommended starting point for a new integration. Its single required query parameter is numeric advertiser_id, sourced from the advertiser_id field in the legacy /agents/list result for the agent. No pagination or filter inputs are documented. The only available response example is labeled HTTP 200 and contains an empty JSON object ({}); it is an unverified source example, with no observed probe response. Recommendation text, author attribution, dates, scores, counts, result ordering, and error fields are not documented. Do not interpret the example as proof of zero recommendations or a guarantee that the route remains available, and do not treat this resource as a recommended-agent search result or a verified rating feed. When planning a move to a current fulfillment_id-based recommendation contract, verify the agent identity and each identifier mapping explicitly instead of equating advertiser_id with fulfillment_id.
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-recommendations-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/agents-get-recommendations-deprecated?key=<API_KEY>&advertiser_id=<advertiser_id>'
Query Result
Use Cases
- Locate older recommendation widgets whose saved requests contain advertiser_id and record which agent each identifier represents.
- Attach the original recommendation lookup context to archived widget content before changing how those records are retrieved.
- Prepare an identity-verified handoff from a legacy recommendation advertiser key to the identifier required by a current recommendation contract.
- Audit recommendation count and rating displays so unsupported response assumptions do not become published social-proof claims.
Frequently asked questions
Which identifier is required to request legacy agent recommendations?
Supply the numeric advertiser_id query parameter. The documented source is the advertiser_id field in the legacy /agents/list result for the intended agent. No additional query parameters are documented for this operation.
Does this operation find agents recommended for a property search?
The documented purpose is to retrieve an agent's recommendations using advertiser_id, not to search for or rank recommended agents. The supplied example does not establish the recommendation item format or ranking semantics.
Are recommendation text, authors, dates, or ratings available in the documented response?
None of those fields are established. The only source example is labeled HTTP 200 and contains {}, and no probe response is available. A recommendation list, score, count, and display ordering must not be assumed from that example.
Does the empty example mean the agent has no recommendations?
No. It is an unverified source example, not an observed recommendation count. It establishes neither an empty-result rule nor current route availability, so it should not be published as a zero-recommendation finding.
Can a legacy advertiser_id be passed unchanged to a current fulfillment_id-based recommendation route?
The supplied facts do not establish that mapping. Confirm the agent identity and the target contract first, then retain the verified crosswalk and cached-content provenance as part of migration.