Organizational Unique ID API
The official RESO Organization Unique Identifier (OUID) provides each individual organization within the Real Estate industry a unique ID alongside the comprehensive list of Realtor Associations, MLSs, system technology partners, technology partners and other affiliated businesses and data providers. The RESO OUID API provides the ability of any organization to query the API and provide back basic organization information and the most important aspect, the Organizational Unique ID. Data providers will include their own OUID in data feeds provided out to those receiving the data so the receivers of the data can accurately identify the organizational source (publisher) of each piece of data in an aggregated database. will be included in RETS data feeds to clearly denote the publisher of the data
There are many business cases for use of the OUID. For Multiple Listing Services and other data providers the purpose is to clearly tag data with the publisher (source) of the data which is distributed to licensed technology partners. For technology partners utilizing data, the OUID assists in managing multiple feeds and overlapping service areas with clear notation of data originator and provides the functionality of de-duplicating content in the data with a notation of the original source of the data allowing the correct data to be kept. In addition, technology partners can utilize the OUID to lookup the MLS(s) who would be a data provider for an Association. A good example is where an Association provides lockbox services and the correct MLS source and underlying data must be linked to the Association lockbox system; lockbox and showing systems often are Association provided services but require MLS data to serve the membership. The RESO Data Dictionary Version 1.5 and beyond will contain standardized containers for the Organizational Unique ID Store at the MLS and technology partner (data distributor).
This API can be used to extract active and inactive information about organizations. Parameters available of querying the dataset are as follows: ouid, active, org, type, city, state, country and zip. This is a public API, no credentials are required to query the Organizational Unique ID dataset. The dataset is updated regularly.
|ouid||Search by Organizational Unique ID.
|assoc2mls||Search by association to an MLS organization.
Example: https://www.reso.org/ouid/?assoc2mls=M00000001 https://www.reso.org/ouid/?assoc2mls=M00000002
|active||Search for active or inactive organizations.
Active: https://www.reso.org/ouid/?active=1 Inactive: https://www.reso.org/ouid/?active=0
|org||Search by an organization’s name or a portion of the name
Example: https://www.reso.org/ouid/?org=mlslistings https://www.reso.org/ouid/?org=Macon County
|type||Search by organization type
Example: https://www.reso.org/ouid/?type=ASSOCIATION https://www.reso.org/ouid/?type=MLS
|city||Search by an organization’s city
|state||Search by the organization’s state.
|country||Search by the organization’s country.
Example: https://www.reso.org/ouid/?country=USA https://www.reso.org/ouid/?country=canada
|zip||Search by an organization’s zip or postal code
|Parameters can be combined to allow specific queries:
|All listings are available by plainly requesting: https://www.reso.org/ouid/
Note: If accessing the OUID database from a third party product the application expects the User Agent header with a valid value.
The XML Markup
<organizations> <organization> <name>Anchorage Board Of Realtors Inc</name> <ouid>A00000002</ouid> <assoc2mls>M00000001</assoc2mls> <type>ASSOCIATION</type> <active>1</active> <url>www.ancboard.com</url> <location> <address>3340 Arctic Blvd. #101</address> <city>Anchorage</city> <state>AK</state> <zip>99503</zip> <country>USA</country> </location> <updated>2017-05-22</updated> </organization> </organizations>
OUID API Update Request Form