Legacy agent profile lookup (deprecated)
View all Realty in US Property & Mortgage Data endpoints →Look up an agent profile through the deprecated profile contract used by older agent directories and CRM records. Both query parameters are required: numeric advertiser_id and string nrds_id, each taken from the corresponding field in a legacy /agents/list result for the intended agent. Keep nrds_id as text rather than treating it as the numeric advertiser identifier. This route is retained for auditing and migrating existing integrations, not recommended for new profile pages. Its available response documentation consists only of an unverified HTTP 200 example containing an empty JSON object ({}). No probe result is available, so profile attributes, biography, contact information, brokerage fields, and error behavior are not established. The example does not verify a missing profile or continued route availability. When comparing with a current profile contract, reconcile the agent identity explicitly; advertiser_id and nrds_id must not be assumed to equal current fulfillment_id or profile_id values. Review only fields confirmed by the applicable contracts before migrating cached profile content.
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-get-profile-deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/agents-get-profile-deprecated?key=<API_KEY>&advertiser_id=<advertiser_id>&nrds_id=<nrds_id>'
Query Result
Use Cases
- Inventory advertiser_id and nrds_id pairs stored in an older agent CRM before changing its profile lookup contract.
- Create a manually confirmed agent identity crosswalk for moving saved directory profiles to a current profile route.
- Audit profile import code that converts digit-only nrds_id strings to numbers and restore the documented textual identifier handling.
- Review cached biography and brokerage panels field by field without treating the empty legacy example as a verified profile schema.
Frequently asked questions
What parameters does the legacy agent profile lookup require?
It requires both numeric advertiser_id and string nrds_id. The documentation obtains each from the same-named field in the legacy /agents/list result. Select a pair associated with the intended agent rather than substituting another type of identifier.
Should nrds_id be sent as a number because its example is numeric?
No. Its documented type is string, while advertiser_id is numeric. Preserve nrds_id as text even if a particular value contains only digits; the two inputs have separate roles.
Can advertiser_id or nrds_id be reused directly as a current profile_id?
The supplied documentation does not establish that equivalence. Verify the agent identity and the current contract explicitly before creating a crosswalk to profile_id or fulfillment_id.
Are biography, brokerage, and contact fields documented in the response?
No such fields are established by the available evidence. The source example is labeled HTTP 200 but contains only {}, and there is no observed probe response. Do not rely on that example for a profile field map or a missing-profile signal.
When is this deprecated profile operation appropriate?
Use its documented contract to audit an existing directory or CRM integration and plan migration. It is not recommended for new profile experiences, and the unverified example does not confirm that the legacy route remains available.