Get listings associated with an agent fulfillment ID

View all Realty in US Property & Mortgage Data endpoints →

Request listings for a selected agent through GET /agents/v2/get-listings. Supply the required string fulfillment_id, documented as coming from /agents/v2/list; the documented input example and default are 1365510. This request takes no documented listing-status filter, date range, limit or offset. No live response was captured for this operation. The supplied HTTP 200 example is a truncated, unverified JSON fragment that contains agent-profile metadata rather than establishing a usable listing collection. Visible source fields include fulfillment_id, fullname, bio and address fields city, country, line, postal_code, state and state_code; broker and office contain their own identity metadata, while ratings and recommendations contain profile metrics. None of these source-only fields is a live-verified response guarantee, and the fragment does not establish listing identifiers, prices, listing status, a listing-array field or pagination metadata. Use this lookup for a selected-agent portfolio workflow only after verifying the returned contract, and do not claim complete inventory, current availability or a distinction between active and sold listings.

API Features

Selected-agent fulfillment-ID input Target the agent selected from the documented /agents/v2/list identity flow using the required string fulfillment_id.
Single-identifier portfolio request The request is documented with one agent identifier only. It does not expose status, date-range or paging parameters for shaping a portfolio.
Source-only profile context The truncated success example contains agent identity, address, broker, office and rating metadata. Treat that fragment as unverified profile context, not an observed listing schema.
Listing collection verification boundary No listing array, property identifiers, prices or pagination fields are established by the supplied fragment. Validate the actual response before rendering portfolio cards.
Portfolio completeness safeguards Keep associated-listing displays separate from claims of exhaustive inventory, current availability or active-versus-sold coverage, none of which is verified here.

Live API Demo

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

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-listings?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

Where should I get fulfillment_id for the agent listing lookup?

The documentation identifies fulfillment_id from /agents/v2/list as the input for this operation. Pass the selected agent identifier as a string. The supplied example and documented default are 1365510; replace that value when looking up another agent.

Can I use advertiser_id or an office ID instead?

No alternative identifier is documented. This operation requires the agent fulfillment_id. The advertiser_id used by legacy review requests and identifiers nested under an office or broker should not be substituted.

Has a listing response been verified for this endpoint?

No live response was captured. The supplied HTTP 200 source example is truncated and contains profile fields such as fulfillment_id, fullname, address, broker, office and ratings. It does not establish a complete response or a usable listing collection.

Can I filter to active listings or page through the portfolio?

No listing-status filter, limit, offset or other paging input is documented. A listing status field, total count and next-page token are also not established by the available source example.

Will this return every property represented by the agent?

Listing completeness, freshness and active-versus-sold coverage are not verified. Do not present results as the entire agent inventory or as proof that a property is currently available.

Should I fetch portfolios for every agent in a search result?

Prefer an explicit lookup after a user selects or shortlists an agent. This follows the documented identifier handoff and avoids treating unverified portfolio data as a required enrichment for every directory result.

Related operations

Guides

View Subscription Plans →