Get recommendations associated with a selected real estate agent

View all Realty in US Property & Mortgage Data endpoints →

Request recommendations for a selected agent using fulfillment_id, a required string query parameter taken from the fulfillment_id field of an /agents/v2/list result. The documented example is 1365510. Do not pass the agent's profile id in place of its fulfillment identifier. No pagination, sorting or recommendation-author filter is documented for this operation. The available documentation example contains a recommendations object with a numeric count and a ratings object containing recommendation_rating, among other profile fields. It is an incomplete profile-shaped example also supplied for the profile and review operations, not an established collection of recommendation entries. Recommendation text, author attribution, dates, entry identifiers and a recommendation-list envelope are not verified by this evidence. No live probe response is available for this operation. Treat recommendations.count and ratings.recommendation_rating as unverified example fields, not a guaranteed response schema or a promise of current totals. Keep recommendations separate from reviews in the interface. Missing feedback or a missing count means unavailable information, not zero endorsements, poor performance or a licensing or trust verdict.

API Features

Fulfillment-keyed recommendation lookup Target the chosen agent with the fulfillment_id returned by agent search, using a required string input rather than the profile identifier.
Separate recommendations view Use a dedicated recommendation request for a recommendations tab instead of presenting review content as interchangeable endorsements.
Documented recommendation count indicator The incomplete documentation example includes recommendations.count as a number; its presence and meaning in a current response still need verification.
Recommendation entry schema guardrails The available profile-shaped example does not establish testimonial text, authors or dates, preventing an unsupported assumption about recommendation cards.
Unknown-versus-zero endorsement handling Design recommendation displays so absent data stays unavailable rather than becoming an invented zero count or a judgment about the agent.

Live API Demo

GET /api/project/realty-in-us/agents-v2-get-recommendations

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-v2-get-recommendations?key=<API_KEY>&fulfillment_id=1365510'
📢
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 recommendations request require?

It requires fulfillment_id as a string. Take it from the fulfillment_id field of the selected /agents/v2/list result. The documented example is 1365510; profile_id is not a documented input for this operation.

Is the recommendation count confirmed by a live response?

No. The incomplete documentation example includes a numeric recommendations.count and a ratings.recommendation_rating field, but there is no live probe response for this operation. Verify these fields in an actual result before depending on them.

Does the example define testimonial text, authors and dates?

No. The supplied example is an incomplete profile-shaped object also used for the other agent detail operations. It does not establish a recommendation-entry list or its text, attribution, date or identifier fields. Do not invent those fields when constructing a testimonial view.

Can I filter or paginate agent recommendations?

No filter, page, offset, limit or sort parameter is documented for this operation. The supported request input is fulfillment_id. The available evidence does not establish completeness or a pagination contract for any returned recommendations.

Should recommendations be combined with reviews or used as a trust score?

No. Keep recommendations distinct from the separate review operation. A recommendation count or missing recommendation data does not establish license status, quality or trustworthiness; an absent count should remain unknown rather than being converted to zero.

Related operations

Guides

View Subscription Plans →