Includes fields commonly used in a Multiple Listing Service (MLS) listing. Some fields are grouped together for viewing convenience, like “Business Group.”
The roster of agents, brokers, appraisers, assistants, affiliates, etc. who are members of the MLS and/or association of REALTORS®.
The roster of offices that are members of the MLS and/or association of REALTORS®.
Clients and other contacts of the member.
The database and informational representation of media, such as photos, virtual tours, documents/supplements, etc.
The transactional history of the listing. A separate record is generated showing the before and after value of any change to each field.
Consumer portals are a common place where contacts and members interact around listings. This resource is used to maintain that relationship by connecting the Contacts and Property resources and providing other information used to maintain the details about client and member interaction around a given listing.
Provides a standard data set for the recording and transfer of event-related information of real estate products, allowing participants to monitor and review their real estate data on a grander scale, quickly and efficiently (i.e., listing views from multiple products).
Provides a means to communicate the saved search criteria and other relative data as it relates to saved search.
These fields are commonly used to record an open house event.
Also known as automatic email, this resource contains the fields supporting a connection between the Contacts and SavedSearch resources, along with the other fields used to send email to the client when the related saved search criteria locates results in the data being queried by the saved search criteria.
Used to represent events that have occurred with records that exist in other resources. A common use case is the deletion or "kill" of a listing record. This resource can be used to show the identity of the deleted record and when it was deleted as well as for other events such as record additions or modifications.
This is a flexible resource that can be used to transmit business and system rules from host to client application. These rules may be meant for human consumption (e.g., Real Estate Business Rules (REBR)), in which case, the client may be a tool allowing a person to review the business rules. The rules may also be meant for machine consumption (e.g., RETS validation) where the rules are structured to be consumed and executed upon by the client application without human intervention.
This is a set of fields that facilitate the passing of scheduled showing events. This resource connects the listing to the member who requested the showing and provides the date and time of the showing.
Covers the name and other information about teams of members who work together.
Accounts for key fields that tie records from the Member Resource to the related records in the Teams Resource.
The Organization Unique Identifier (OUID) – now known as the Unique Organization Identifier (UOI) – provides a common ID system for organizations that exchange data in the real estate space.
Adding notes about a given listing is a common interaction between the contact and member within a consumer portal. ContactListingNotes is a subset to the ContactListings Resource allowing for multiple notes from the contact or the member to be stored around a given listing.
Some systems may allow the input of more than one "other" phone for a given contact or member. In those cases, a collection may be used for any number of other phone numbers with information about what type of number is included.
Properties can have different performance ratings applied to them. This resource allows the relation of multiple ratings to the given individual listing.
A property might have different means of producing power, whether different systems, like a solar and wind system, or more than one of a given system, like two different solar systems. This resource allows for the relation of multiple power production systems to a single property.
In cases where detailed information about separate rooms in a property are collected, this data is commonly stored in a relational table. This prevents an overly wide property table and also allows for an unlimited number of rooms that can be detailed.
With residential income, aka multifamily properties, each type of unit can have a number of describing fields. In cases where the number of unit types grows, a relational structure is important.
Some systems may allow for the input of more than one type of social media for a given member, office, contact, etc. In those cases, a collection of social media records may be related to the member, office or other kind of record.
Provides a series of fields pertaining to the local real estate trade association.
Provides the joining information to relate the Member and Association resources to each other.
Provides the joining information to relate the Office and Association resources to each other.
Offers an alternative to timestamps with an event log, providing an OData-compliant logical timestamp methodology on top of events and any resources or entities that the events affected. The logical timestamp is an event identifier that denotes that a business event occurred (e.g., listing price change, listing status change, phone number change, deletion of a photo).
Communicates lockbox, smart lock and showing agent information.
Can be used to advertise metadata about the available fields on a given server in a way that is predictable and user friendly.
Can be used to convey metadata about lookups (enumerations) available on a given server, providing a streamlined way to deliver enumeration metadata to the consumer.
A list of lookup (enumeration) fields with defined lookup values included in the Data Dictionary.
Resource Field Counts
Page Revision Date: Jun 10 2022