Trestle RESO Web API
The primary Trestle interface — a RESO Web API 2.0 / OData 4.0 endpoint that republishes MLS data mapped to the RESO Data Dictionary. The anonymously readable OData service document advertises 18 entity sets: Property, Office, Member, Media, OpenHouse, CustomProperty, PropertyRooms, PropertyUnitTypes, Teams, TeamMembers, Field, Lookup, Model, PropertyGreenVerification, Building, HistoryTransactional, DataSystem and Enumeration. Authentication is OAuth2 client_credentials against /trestle/oidc/connect/token with scope=api, returning an 8-hour Bearer token. Documented quotas are 7,200 queries/hour and 180 queries/minute for the Web API and 18,000/hour and 480/minute for media URLs; live 401 responses carry Minute-Quota-Limit and Hour-Quota-Limit headers. The service document is public; the $metadata document and every entity set require a Bearer token issued only after an MLS data licence is signed.