Select Page

RESO Certification Processes and Policies

<< See Main RESO Certification Page

Testing MLS Software Platforms: MLS software vendors (providers) pre-test their own systems with RESO’s software to ensure they are in compliance with current standards. Providers then forward results to their MLS customers (recipients) for approval. 

Publishing MLS Certifications: MLSs (and other certification recipients) will receive requests for certification approval via email. Upon approval, certification endorsement results are published on RESO’s website. Contact certification@reso.org with any questions.

Qualifying for Certification: Certification endorsements are available to RESO members and paid non-members. Recipients must agree to RESO’s Certification Terms and Conditions as well as Declaration of Use. Certification endorsements are complimentary for RESO members in good standing. Non-member fees are identified in the RESO Certification Fee Schedule

Provider Maintenance of Recipient Endorsements: Providers are responsible for maintaining their active customers and endorsements in the RESO Certification System. Providers have the ability to archive customers when they are no longer active. When endorsements are archived, their status will be updated on RESO’s public site.

MLS-Specific Certification Requirements: MLS software providers MUST obtain both Web API Core and Data Dictionary endorsements to receive RESO Certification. Other software providers may choose endorsements most suited for their business cases.

Web API vs Data Dictionary Testing: MLS software providers are tested once per distinct USI (Unique System Identifier) for the Web API Core endorsement, then each MLS is tested for the Data Dictionary endorsement on that system.

Standard Data Elements Required Conformance: The RESO Data Dictionary certification process identifies cases where providers have data elements that should adhere to current standards. If a local resource, field, or enumeration is found to match a RESO standard data element during testing, RESO may require the provider to add that standard mapping. The local value may be retained for backwards compatibility, but the standard element must be present as well.

Identifying Nonconformance: RESO may use a number of techniques to ensure adherence to standards, from data-driven, substring, or text-similarity matching to manual review, machine learning, or consumer reporting. RESO continuously monitors data being collected during the certification process and engages the community to ensure that variations from the standard are identified and addressed. 

Certification Revocation: RESO endorsements may be revoked at any time if a provider is found to be out of compliance with its current endorsements. Certified systems must be available in production to authorized customers. Notifications will be sent to the provider and recipient upon revocation of any endorsement.

Rectifying Nonconformance: Providers and recipients will be notified when there is a compliance issue and will have 14 days to respond with a plan of action. These systems must be tested again within 30 days from the date of notification to maintain their certification status.

Appeals: There is an appeal process for providers and recipients in cases when there is a disagreement about a local field or enumeration that might be miscategorized as a RESO standard data element. Please contact certification@reso.org if you have any questions.

System Performance Reporting: Providers MAY opt out of publishing their Data Dictionary server performance metrics publicly, but the results will be visible to the recipients of the endorsement. Anonymous industry aggregates for performance allow providers to improve services for data consumers.

Retention/Removal of Data: Except for applicants’ resource endpoints, credentials, metadata, certification results, and data availability reports, certification data shall be expunged immediately and permanently upon completion of certification testing.