Author: Kevin

NAR recently mandated that MLSs be able to provide all licensed data for multi-participant feeds (e.g., IDX, VOW, BBO) to their members in a single feed, instead of separate feeds for each.

To assist MLSs in fulfilling this mandate, Bridge now allows MLSs to provision access to multiple feed types within a single data approval. This means that, instead of ingesting separate IDX, VOW, BBO, and other feeds from a single MLS, data recipients may now pull just one feed, and use new metadata to determine appropriate licensing at the record and field level.

To that end, we will be adding two additional data points to all existing MLS feeds.  

FeedTypes field:

A new field will be added to each record returned by the API: “FeedTypes”. This is an array that will indicate whether the record is sourced from a IDX, VOW, BBO, AVM, and/or PDAP feed type. 

For example, if a listing is in the combined feed that is originally in a “VOW” feed, then FeedTypes would return [‘VOW’]. If the listing is also part of the IDX feed, the new field would return [“IDX”, “VOW”].

Note this field will appear in all resources of all MLS datasets, regardless of whether the MLS has provisioned a combined feed. If the MLS has not yet set metadata values, the field will be an empty array.

FieldRules resource:

A new resource named FieldRules will be available on all MLS datasets. Hitting this endpoint will allow you to answer the questions: which license type determines the rules for this field, and which fields are part of a specific license type. Data recipients will only see the license types for which they have been approved.

Combined feeds are set upon request and at the MLS’s discretion.

We are expecting this update to be available after the 16th of August, at which time additional documentation will be provided.

This weekend we had two incidents with our Elasticsearch clusters that left our MLS data APIs temporarily unavailable. Note no data was lost and all datasets are back at full capacity. Other APIs were unaffected.

We apologize for the stress – please know that we are taking steps to mitigate future outages of this nature, as well as reduce downtime when such incidents do occur

Friday April 9th: 5:02 – 5:45 UTC-7 (PST)
Saturday April 10th: 5:23 – 8:00 UTC-7 (PST)

Please note an upcoming change to our OData XML metadata across all MLS datasets.

Enumeration names will no long contain spaces, and instead strings will be included as part of field annotations. For example:

<Member Name="Bob Realtor">

will now be presented as

<Member Name="Bob_Realtor">
<Annotation Term="RESO.OData.Metadata.StandardName" Qualifier="_0" String="Bob Realtor"/>
</Member>

This change will be made on January 31st 2021. Note this will not require any changes to your API queries, but will require you to update your implementation if you use Metadata names directly.

To support users who have not yet been able to update their API integration for the deprecation of legacy endpoints, we will been keeping these endpoints active until January 1st 2020.

The following API endpoints are now deprecated and are scheduled to be unavailable on November 1, 2020. Please note that this only affects the legacy Bridge Web API for MLS data, not the RESO Web API.

/{dataset}/summary 
/{dataset}/listings/maps
/{dataset}/listings/cluster
/{dataset}/listings/{listingId}/agent
/{dataset}/listings/{listingId}/office
/{dataset}/agents/{agentId}/listings
/{dataset}/offices/{officeId}/agents
/{dataset}/offices/{officeId}/listings
/{dataset}/openhouses/{openhouseId}/listing
/{dataset}/openhouses/{openhouseId}/agent

Additionally, Public Records Comparables will no longer be available after November 1, 2020.

/parcels/{parcelId}/comps

We are updating our XML Metadata to be in line with RESO Data Dictionary Testing Standards. This may cause errors in some OData libraries with strict verification settings due to presence of unexpected facets.

Platform and API documentation has been updated and is available at https://bridgedataoutput.com/docs.

If you have any comments, questions or feedback, please reach out to us at api@bridgeinteractive.com

OData Metadata has been updated to show when a field is a collection of enumerable values. This changes the “Type” of fields like Appliances from “PropertyEnums.Appliances” to “Collection(PropertyEnums.Appliances)”. Single value fields like “StandardStatus” remain the same.

MLS data consumers are now able to make API queries against all fields, not just RESO Data Dictionary fields. This provides users with additional levels of flexibility when using the API for MLS listing data.

The Zestimate API now returns the Forecast standard deviation with each result.

Forecast standard deviation represents the best measure of expected accuracy of an AVM. It is the AVM’s expected (forecasted) proportional standard deviation around actual subsequent sales price for the given properly value estimate.