In order to better meet the latest OData specification and support RESO certification, we’re rolling out a small change to collections in the Bridge API. This will impact both the RESO Web API and “classic” Bridge API.
Previously, users may have seen null collections in cases where the field was unavailable from the upstream data provider. Going forward, instead of null values, Bridge API will return empty arrays: []
This will roll out incrementally across records and datasets as listing data is naturally reprocessed from upstream servers; users can expect to see both styles until all data is reimported.