Homera RESO certification
Running production checks.
Loading provider, metadata, field coverage, sync, and infrastructure evidence.
Homera RESO certification
Loading provider, metadata, field coverage, sync, and infrastructure evidence.
Live evidence for the Web API provider, Data Dictionary metadata, Bridge sync, and the final RESO submission handoff.
Technical checks
Technical status
Ready for Commander
Submission status
Awaiting RESO IDs
Items needing action
3
Open any suite to see the exact pass condition and live result.
The seven authenticated requests RESO Commander needs before a certification run.
Service document
Passed
Pass condition
Authenticated GET returns HTTP 200 and the OData service document.
Evidence
HTTP 200 · 44 ms
$metadata endpoint
Passed
Pass condition
Authenticated GET returns HTTP 200 XML metadata.
Evidence
HTTP 200 · application/xml; charset=utf-8 · 28 ms
Property sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns a record array and numeric @odata.count.
Evidence
HTTP 200 · 20,000 records · 64 ms
Office sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns a record array and numeric @odata.count.
Evidence
HTTP 200 · 1,032 records · 338 ms
Member sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns a record array and numeric @odata.count.
Evidence
HTTP 200 · 15,731 records · 3,571 ms
OpenHouse sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns a record array and numeric @odata.count.
Evidence
HTTP 200 · 4,976 records · 1,185 ms
Lookup sample and count
Passed
Pass condition
GET with $top=1 and $count=true returns a record array and numeric @odata.count.
Evidence
HTTP 200 · 31 records · 132 ms
EDMX, entity keys, entity sets, lookup annotations, and field facets.
Metadata is non-empty XML
Passed
Pass condition
An EDMX document larger than 100 bytes is returned.
Evidence
18,528 bytes received
OData EDMX 4.0 root
Passed
Pass condition
The root declares EDMX version 4.0.
Evidence
edmx:Edmx Version=4.0
DataServices container
Passed
Pass condition
Metadata includes an edmx:DataServices container.
Evidence
edmx:DataServices present
Schema declaration
Passed
Pass condition
At least one OData Schema is declared.
Evidence
2 schema declaration(s)
Entity types declared
Passed
Pass condition
At least one EntityType is declared.
Evidence
5 entity type(s)
Property has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
ListingKey is the key
Property key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
ListingKey
Office has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
OfficeKey is the key
Office key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
OfficeKey
Member has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
MemberKey is the key
Member key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
MemberKey
OpenHouse has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
OpenHouseKey is the key
OpenHouse key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
OpenHouseKey
Lookup has a key
Passed
Pass condition
Each resource declares an OData Key.
Evidence
LookupKey is the key
Lookup key is a property
Passed
Pass condition
The declared key also exists as a Property.
Evidence
LookupKey
Property entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Property
Property entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Property
Office entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Office
Office entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Office
Member entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Member
Member entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Member
OpenHouse entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.OpenHouse
OpenHouse entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
OpenHouse
Lookup entity set advertised
Passed
Pass condition
The service advertises the required EntitySet.
Evidence
Homera.RESO.Lookup
Lookup entity type resolves
Passed
Pass condition
The EntitySet points to a declared EntityType.
Evidence
Lookup
LookupName annotations
Passed
Pass condition
Lookup fields include RESO LookupName annotations.
Evidence
63 annotation(s)
Decimal precision facets
Passed
Pass condition
Every Edm.Decimal field declares Precision.
Evidence
9 decimal field(s) checked
String length facets
Passed
Pass condition
Every Edm.String field declares MaxLength.
Evidence
91 string field(s) checked
Advertised fields compared with upstream metadata refreshed 7/22/2026, 5:06:52 PM.
Property field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
124/124 fields present
Office field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
10/10 fields present
Member field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
19/19 fields present
OpenHouse field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
14/14 fields present
Lookup field coverage
Passed
Pass condition
Every field advertised in Homera metadata exists in the upstream dataset.
Evidence
6/6 fields present
Latest full dataset imports used by the certification provider.
Property full sync
Passed
Pass condition
The latest sync completed with HTTP 200 and stored at least one record.
Evidence
20,000 full-sync records · HTTP 200
Office full sync
Passed
Pass condition
The latest sync completed with HTTP 200 and stored at least one record.
Evidence
1,032 full-sync records · HTTP 200
Member full sync
Passed
Pass condition
The latest sync completed with HTTP 200 and stored at least one record.
Evidence
15,731 full-sync records · HTTP 200
OpenHouse full sync
Passed
Pass condition
The latest sync completed with HTTP 200 and stored at least one record.
Evidence
4,976 full-sync records · HTTP 200
OAuth and the production Convex dependency are reachable.
OAuth client credentials
Passed
Pass condition
The provider mints a bearer token without exposing credentials.
Evidence
OAuth token minted in 106 ms
Convex production health
Passed
Pass condition
The public dependency health endpoint returns HTTP 200.
Evidence
HTTP 200 · 154 ms
Identifiers issued by RESO after the certification request is opened.
Provider UOI
Pending
Pass condition
RESO assigns the technology provider organization identifier.
Evidence
Request from dev@reso.org
Recipient UOI
Pending
Pass condition
RESO confirms the organization receiving certification.
Evidence
Request from dev@reso.org
Provider USI
Pending
Pass condition
RESO assigns the provider system identifier used in submission.
Evidence
Request from dev@reso.org
What remains
Request identifiers
Ask dev@reso.org for the provider UOI, recipient UOI, and provider USI.
Run certification
Generate the private inputs, then run Web API Core before Data Dictionary.
Approve results
Submit the passing reports and complete the recipient terms approval.