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
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-v2-get-recommendations 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'
Query Result
Use Cases
- Load a recommendations tab only after a user chooses an agent and the application has retained that result's fulfillment_id.
- Build a professional-comparison screen with recommendations and reviews in separately labeled sections instead of combining their counts or content.
- Prototype an endorsement-count badge from recommendations.count only after checking the actual returned field; use an unavailable state when the field is missing.
- Evaluate whether recommendation cards are supportable by checking for actual entry text and attribution rather than fabricating them from the profile-shaped documentation example.
- Keep a consented agent record's recommendation status distinct from licensing or trust assessments, especially when no recommendation information is returned.
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.