This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
Not from the company, and here with a question? You are welcome here — we would rather be the front line and point you the right way than have a good report go nowhere. What this repository can answer is narrow, though, so it is worth knowing who you are actually looking for:
- A question about how the API works, an account, billing, or a bug in the service — that is the company's own support, not us. We profile this API; we do not operate it and cannot see your account.
- A bug in an open-source project we only catalog — file it on that project's own repository. This has happened with a real and correct bug report that reached us instead of the people who could fix it, which helped nobody.
- Anything about this listing itself — the description, the tags, the rating, a missing or wrong artifact — is ours. Open an issue here.
- Not sure, or something general about API Evangelist or APIs.io — open an issue on the APIs.io Inbox and we will route it.
This repository contains no software, and we will never ask you to download anything. There is no build, release, installer, or binary here — only text and machine-readable API descriptions, so there is nothing here that can be "corrupt" or need "repairing". Any issue, comment, or email claiming otherwise and offering a download link is not from us and is hostile. Do not follow the link; it is a lure. Report it to GitHub and, if you like, tell us at info@apievangelist.com so we can take it down.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
Trestle is the real estate data distribution platform operated by CoreLogic (rebranded Cotality in 2025), sitting between roughly 500 US Multiple Listing Services and the technology providers, brokers and aggregators that consume their listing data. Its home market is the United States. Trestle occupies the licensing-and-transport layer of the residential real estate value chain: it maps each participating MLS into the RESO Data Dictionary and republishes it through a RESO Web API 2.0 / OData 4.0 endpoint and a legacy RETS 1.8 endpoint, plus a bidirectional Direct Web API into the Matrix MLS CRM and a Participant Reporting API used to prove broker relationships back to the MLSs. Its API posture is unusually honest for this sector: the documentation portal is fully public and needs no login, the OAuth2 client-credentials flow and every OData query convention are published openly, and the OData service document answers anonymously with a 200. But nothing behind it is reachable. The $metadata document and every entity set return 401 Bearer, and credentials are only issued after a developer registers a Technology Provider or Broker account, requests a connection to a specific multiple listing organization, and completes an e-signed data licence contract that all parties sign — a contract most MLSs will only ratify if a licensed broker or agent sponsors it or the technology provider files periodic participant reports. Trestle is RESO-certified and publicly documented, and still effectively uncallable without a signed licence. Certification is not reachability.
APIs.json: https://raw.githubusercontent.com/api-evangelist/trestle/refs/heads/main/apis.yml
- Real Estate
- United States
- MLS
- RESO
- Property Listings
- IDX
- PropTech
- Data Distribution
- OData
- RETS
- Listing Syndication
- Created: 2026-07-26
- Modified: 2026-07-26
- RESO Web API: Platinum certification for the Trestle Web API listing transmission service.
- RESO Data Dictionary: v2.0 vendor certification, achieved 2024-10-11.
- RESO UPI: first multiple listing data distributor certified on UPI v2.0.
- Reachability: the OData service document at
https://api.cotality.com/trestle/odatais anonymously readable (200). The$metadatadocument and every entity set return 401 Bearer. Certified per the public record, but no endpoint is reachable without an MLS data licence agreement.
Licence agreement. Register a Technology Provider or Broker account at https://trestle.corelogic.com, then request a connection to each individual multiple listing organization. Trestle walks the applicant through an e-signing contract collecting signatures from all parties and authorizing billing of that MLO's licence fee. Most MLOs additionally require a licensed broker or agent to ratify the contract, or periodic participant reports naming which members use the service. Credentials are tied to a specific product/feed type. No sandbox is documented.
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.
- Human URL: https://trestle-documentation.corelogic.com/webapi.html
- Base URL:
https://api.cotality.com/trestle/odata
- RESO
- OData
- Property Listings
- MLS
- Real Estate
- Documentation
- API Reference
- OData Service Document
- Documentation — RESO Common Format
- Documentation — Web API at Scale
- Documentation — Web API Libraries
- Data Model
- Enumerations
A bidirectional OData interface into the Matrix MLS database, separate from the RESO feed. The CRM reference documents Contacts, EmailHistory, Lists, PortalContents, SavedSearches, UserRegistry and an aggregated DashboardAPI with read and write operations; a companion MLO reference covers multiple-listing-organization integration. Authentication is OpenID Connect, with Clareity Single Sign-On authorization and HTTP Basic named as alternatives, and access is further constrained by the acting user's privileges in Matrix. No explicit base URL is published in the reference, so none is asserted here.
- Matrix MLS
- CRM
- OData
- Real Estate
A compliance API that lets technology providers report to each MLS which brokers they hold contracts with — the mechanism by which the licence relationship behind a data feed is evidenced. Documented operations are POST and GET on /trestle/report/TpParticipantReport, authenticated with the same OAuth2 client_credentials flow as the Web API (scope=api for Web API feeds, scope=rets for RETS feeds). Not every MLS uses it; some require individual contracts hosted in Trestle instead.
- Human URL: https://trestle-documentation.corelogic.com/participant-reporting-api.html
- Base URL:
https://api.cotality.com/trestle/report
- Compliance
- Reporting
- MLS
- Real Estate
Trestle's legacy Real Estate Transaction Standard interface, documented as compliant with RETS 1.8. RESO no longer updates the RETS specification, but Trestle continues to serve it for customers who cannot move to the Web API. Login is POST /trestle/rets/login; the service is session-less and supports either HTTP Basic with a Base64-encoded client_id:client_secret or an OAuth2 bearer token obtained with scope=rets. Digest authentication is explicitly not supported.
- Human URL: https://trestle-documentation.corelogic.com/rets.html
- Base URL:
https://api.cotality.com/trestle/rets
- RETS
- Legacy
- MLS
- Real Estate
- Website
- Documentation
- FAQ
- Sign Up
- Login
- Support
- Certification — RESO Data Dictionary v2.0
- Certification — RESO Platinum Web API
- Kin Lane — kin@apievangelist.com