Trestle

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 at trestle-documentation.corelogic.com 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 at api.cotality.com/trestle/odata 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.

Trestle publishes 4 APIs on the APIs.io network. Tagged areas include Real Estate, United States, MLS, RESO, and Property Listings.

Trestle’s developer surface includes documentation, FAQ, signup flow, support, getting-started guide, API reference, engineering blog, and 31 more developer resources.

40.4/100 thin ▬ flat Agent 39/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
4 APIs
Real EstateUnited StatesMLSRESOProperty ListingsIDXPropTechData DistributionODataRETSListing Syndication

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 40.4/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 12.6 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 10.6 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 39/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/trestle: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

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 docu...

Trestle Direct Web API

A bidirectional OData interface into the Matrix MLS database, separate from the RESO feed. The CRM reference documents Contacts, EmailHistory, Lists, PortalContents, SavedSearch...

Trestle Participant Reporting API

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...

Trestle RETS

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...

Postman Collections 1

Ready-to-run Postman collections for exercising this provider's APIs.

Rate Limits 1

Documented rate limits and quota policies.

Trestle Rate Limits

4 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Trestle Authentication

oauth2/openIdConnect/http · 4 schemes

SECURITY

Trestle Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Trestle Scopes

3 scopes · clientCredentials/authorizationCode

3 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 8

Authentication, authorization, and security posture

Scroll for all 8

Operate 7

Status, limits, changes, and where to get help

Scroll for all 7

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: trestle
url: https://raw.githubusercontent.com/api-evangelist/trestle/refs/heads/main/apis.yml
name: Trestle
kind: company
description: '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 at trestle-documentation.corelogic.com 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 at
  api.cotality.com/trestle/odata 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.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/corelogic.png
tags:
- Real Estate
- United States
- MLS
- RESO
- Property Listings
- IDX
- PropTech
- Data Distribution
- OData
- RETS
- Listing Syndication
created: '2026-07-26'
modified: '2026-07-26'
enriched: '2026-07-26'
specificationVersion: '0.19'
apis:
- aid: trestle:trestle-reso-web-api
  name: Trestle RESO Web API
  description: '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.'
  humanURL: https://trestle-documentation.corelogic.com/webapi.html
  baseURL: https://api.cotality.com/trestle/odata
  tags:
  - RESO
  - OData
  - Property Listings
  - MLS
  - Real Estate
  properties:
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/webapi.html
  - type: APIReference
    url: https://trestle-documentation.corelogic.com/webapi-reference.html
  - type: ODataServiceDocument
    url: openapi/trestle-odata-service-document.json
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/reso-common-format.html
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/webapi-at-scale.html
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/webapi-libraries.html
  - type: DataModel
    url: https://api.cotality.com/trestle/Documentation/MetaData/Resource/Property
  - type: Enumerations
    url: https://api.cotality.com/trestle/Documentation/MetaData/Enums
- aid: trestle:trestle-direct-web-api
  name: Trestle Direct Web API
  description: 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.
  humanURL: https://trestle-documentation.corelogic.com/direct-webapi-crm-reference.html
  tags:
  - Matrix MLS
  - CRM
  - OData
  - Real Estate
  properties:
  - type: APIReference
    url: https://trestle-documentation.corelogic.com/direct-webapi-crm-reference.html
  - type: APIReference
    url: https://trestle-documentation.corelogic.com/direct-webapi-mlo-reference.html
- aid: trestle:trestle-participant-reporting-api
  name: Trestle Participant Reporting API
  description: 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.
  humanURL: https://trestle-documentation.corelogic.com/participant-reporting-api.html
  baseURL: https://api.cotality.com/trestle/report
  tags:
  - Compliance
  - Reporting
  - MLS
  - Real Estate
  properties:
  - type: APIReference
    url: https://trestle-documentation.corelogic.com/participant-reporting-api.html
- aid: trestle:trestle-rets
  name: Trestle RETS
  description: 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.
  humanURL: https://trestle-documentation.corelogic.com/rets.html
  baseURL: https://api.cotality.com/trestle/rets
  tags:
  - RETS
  - Legacy
  - MLS
  - Real Estate
  properties:
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/rets.html
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/rets-libraries.html
  - type: Documentation
    url: https://trestle-documentation.corelogic.com/rets-connector.html
common:
- type: DomainSecurity
  url: security/trestle-domain-security.yml
- type: Website
  url: https://www.cotality.com/products/trestle
- type: Documentation
  url: https://trestle-documentation.corelogic.com/
- type: FAQ
  url: https://trestle-documentation.corelogic.com/faq.html
- type: SignUp
  url: https://trestle.corelogic.com/SubscriptionWizard
- type: Login
  url: https://trestle.corelogic.com/Login
- type: Support
  url: https://www.cotality.com/support
- type: Email
  url: mailto:trestlesupport@cotality.com
- type: Certification
  url: https://www.cotality.com/resources/article/corelogic-achieves-reso-data-dictionary-v2-0-vendor-certification
  name: CoreLogic achieves RESO Data Dictionary v2.0 vendor certification (2024-10-11)
- type: Certification
  url: https://www.reso.org/blog/corelogic-trestle-achieves-reso-platinum-certification-2/
  name: CoreLogic Trestle achieves RESO Platinum certification
- type: DeveloperPortal
  url: https://trestle-documentation.corelogic.com/
  name: Trestle developer documentation portal (public, no login)
- type: GettingStarted
  url: https://trestle-documentation.corelogic.com/webapi.html
  name: Getting Started with Trestle WebAPI
- type: APIReference
  url: https://trestle-documentation.corelogic.com/webapi-reference.html
  name: Trestle WebAPI Reference (OData conventions + Trestle extensions)
- type: Blog
  url: https://www.cotality.com/insights
  name: Cotality Insights
- type: TermsOfService
  url: https://www.cotality.com/legal/terms-of-use
- type: PrivacyPolicy
  url: https://www.cotality.com/legal/privacy-policy
- type: StatusPage
  url: https://status.cotality.com
  name: Cotality US status page (PagerDuty) — company-wide, not Trestle-specific
- type: Deprecation
  url: https://trestle-documentation.corelogic.com/
  name: Host migration notice — api-prod/api-trestle.corelogic.com deprecated in favour of api.cotality.com with 30-day notice
- type: Security
  url: https://www.cotality.com/legal/responsible-disclosure-policy
  name: Cotality Responsible Disclosure Policy (Bugcrowd submission form)
- type: VulnerabilityDisclosure
  url: security/trestle-vulnerability-disclosure.yml
- type: Compliance
  url: https://www.cotality.com/resources/article/corelogic-achieves-reso-data-dictionary-v2-0-vendor-certification
  name: RESO certifications — Web API Platinum, Data Dictionary v2.0, UPI v2.0
- type: Conformance
  url: conformance/trestle-conformance.yml
- type: Authentication
  url: authentication/trestle-authentication.yml
- type: OAuthScopes
  url: scopes/trestle-scopes.yml
- type: OpenIDConnect
  url: well-known/trestle-openid-configuration.json
  name: OIDC discovery document (anonymous, HTTP 200)
- type: WellKnown
  url: well-known/trestle-well-known.yml
- type: Packages
  url: packages/trestle-packages.yml
  name: Client libraries (all third party — Trestle ships no first-party SDK)
- type: ErrorCatalog
  url: errors/trestle-problem-types.yml
- type: Lifecycle
  url: lifecycle/trestle-lifecycle.yml
- type: ChangeLog
  url: changelog/trestle-changelog.yml
- type: ChangeLog
  url: https://trestle-documentation.corelogic.com/
  name: Trestle release notes and Content Patches
- type: Conventions
  url: conventions/trestle-conventions.yml
- type: DataModel
  url: data-model/trestle-data-model.yml
- type: RateLimits
  url: rate-limits/trestle-rate-limits.yml
- type: Postman
  url: postman/trestle-webapi.postman_collection.json
  name: Trestle WebAPI Demonstration (published Postman collection)
- type: Examples
  url: examples/trestle-webapi-examples.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/trestle-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com