Thank you to everyone who has taken the time to evaluate the changes available on our UAT environment.
We’re reviewing developer feedback specifically on the $top changes we announced that will bring the Bridge API in line with OData standards and the RESO Web API 2.1.0 Core specification.
We understand and agree that it’s a significant change to current functionality and, though in line with upcoming industry specifications, introduces a key discrepancy between Bridge and other industry API providers at present.
To ease the transition, we’re planning to implement versioning on Bridge API endpoints. This will allow data consumers to request the new $top behavior from a new RESO Web API 2.1 endpoint if desired, or continue to pull from the current RESO Web API 2.0 endpoint where the currently-available $top behavior will remain the default for the time being.
Please anticipate more technical details on this in the coming week. For now, expect that the November 19 production release will not include the $top changes available on UAT. We sincerely appreciate your time and feedback.