Get a selected real estate agent's professional profile
View all Realty in US Property & Mortgage Data endpoints →Retrieve an agent profile using the required profile_id query parameter, taken from the id field of an /agents/v2/list result. The optional fulfillment_id comes from that result's fulfillment_id field. Keep these identifiers separate; a profile ID and a fulfillment ID are not interchangeable. The documented profile_id example is 56d09a4b2cfde1010000abb1, while fulfillment_id has no supplied default. The available documentation example shows profile identifiers id and _id; fullname, profile_name, bio and profile_description; an address object with line, city, postal_code, state, state_code and country; agent_represents.buyer and agent_represents.seller booleans; an areas_served string; and languages and licenses arrays whose item structures are not established by the empty sample arrays. It also shows broker and office objects with name and fulfillment_id, photo.href, and meta.last_update_date. Feedback-related fields include recommendations.count and a ratings object with average_rating, overall_rating, reviews_count and responseCount. The sample mixes numeric and string rating values, so do not assume one numeric type for every ratings field. These are unverified documentation fields, not observed live-response guarantees: no probe response is available for this operation, and the supplied example is incomplete. Handle absent fields and do not infer current contact details, license validity, photo usage rights or a complete professional history from a returned profile. Retrieve recommendations and reviews through their separate operations when those are the intended views.
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-profile API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/agents-v2-get-profile?key=<API_KEY>&profile_id=56d09a4b2cfde1010000abb1'
Query Result
Use Cases
- Open a professional detail panel after a user selects an agent from /agents/v2/list, passing the selected id as profile_id rather than as fulfillment_id.
- Enrich a consented CRM record with returned biography and office information while preserving missing values instead of fabricating contact details.
- Build a buyer-versus-seller representation section when the documented agent_represents flags are present, without interpreting those flags as license verification.
- Maintain separate profile and fulfillment identifier columns so later recommendation or review lookups do not accidentally receive a profile ID.
- Show the returned meta.last_update_date as profile metadata, without presenting it as a guarantee that every professional detail is current.
Frequently asked questions
Where do I get profile_id for this request?
Use the id field of the selected result from /agents/v2/list. profile_id is a required string. The documented example is 56d09a4b2cfde1010000abb1; an actual lookup should use the identifier of the agent the user selected.
Is fulfillment_id required to get an agent profile?
No. This operation requires profile_id and accepts fulfillment_id as an optional string from the agent-list result's fulfillment_id field. No fulfillment_id default is supplied for the profile request. Do not exchange the two identifiers.
Which professional details are documented in the response?
The incomplete documentation example includes profile names and biography, address, areas_served, buyer and seller representation flags, broker and office objects, photo.href and meta.last_update_date. It also contains languages and licenses arrays, but their empty example values do not define an item schema. None of these fields was confirmed by a live response for this operation.
Does a profile confirm that an agent has a valid license?
No. A returned profile, representation flag or licenses field is not a licensing determination. The available example does not establish the structure or verification status of license records, so check the relevant licensing authority separately when that assurance is needed.
Can I treat the profile's ratings as complete reviews?
No. The example contains rating summaries and recommendations.count, not an established collection of review entries. Some rating values are strings and others are numbers. Use the separate review or recommendation operation for those views and verify the returned structure before rendering individual feedback.