Get legacy agent reviews by advertiser ID (deprecated)

View all Realty in US Property & Mortgage Data endpoints →

Request agent reviews through the deprecated GET /agents/get-reviews route. The only documented input is the required numeric advertiser_id, which the legacy /agents/list route is documented to return. Do not substitute an agent fulfillment_id for this identifier. The available HTTP 200 source example is an empty JSON object, so it establishes no review collection, review text, rating, timestamp, author attribution or pagination fields. No live response was captured for this operation; the empty example is not evidence that a particular agent has no reviews. Retain this route only when auditing or migrating an existing advertiser-ID review workflow, and verify availability and response structure before relying on it.

API Features

Advertiser-ID review lookup Address the legacy review request with its required numeric advertiser_id rather than an agent name, ZIP code or fulfillment_id.
Legacy directory-to-review handoff Follow the documented identifier relationship from /agents/list to /agents/get-reviews when reviewing an existing integration; the supplied examples do not verify populated records.
Empty-object review evidence boundary The provided success example is {}, not a documented review array. Review text, scores, dates and author fields remain unverified.
Deprecated review migration scope Keep this operation identifiable as a retained migration surface, without promising continued availability or recommending it for new review products.

Live API Demo

GET /api/project/realty-in-us/agents-get-reviews-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-get-reviews-deprecated?key=<API_KEY>&advertiser_id=<advertiser_id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Which identifier does the legacy review request require?

It requires advertiser_id as a numeric query parameter. The documented source of that value is the legacy /agents/list operation. An agent fulfillment_id is a different identifier and is not documented as a substitute.

Does the empty success example mean an agent has no reviews?

No. The supplied HTTP 200 example is only an empty object and was not a live response for this operation. It does not establish whether reviews exist for any particular advertiser_id.

Which review fields can I rely on?

No populated review fields are established by the available example. Review text, rating values, timestamps, reviewer attribution and pagination must be verified before a client depends on them.

Can I filter or paginate reviews with this operation?

No filter or pagination input is documented here. The only documented query parameter is advertiser_id; do not assume limit, offset or rating filters are supported.

Should a new agent-review application use this route?

This route is deprecated and was not live-tested. Treat it as a legacy audit or migration surface, not a recommended foundation for a new review application or a guarantee of continued service.

Related operations

Guides

View Subscription Plans →