# Yardi Canada > Yardi Canada Ltd. is the Canadian subsidiary of Yardi Systems (Goleta, California) — Toronto HQ, offices in Saskatoon and Vancouver, roughly 500 staff — selling and supporting the Yardi property and investment management stack in Canada: Voyager, Breeze Premier, RentCafe, Home IQ, Matrix and Pulse. It is a system of record for landlords and asset managers, not a listing portal and not a land registry. Its API posture is licensed-access-only: there is no public developer portal and no published REST contract. What IS public, and what changes the picture, is an official MCP server — the Yardi Virtuoso Connector — plus a region-sliced status API that exposes Canadian service health anonymously. Generated by API Evangelist on 2026-07-26 from apis.yml and the artifacts in this repository. Yardi serves no llms.txt of its own — notably, https://www.yardi.com/robots.txt carries an AI-crawler policy that repeatedly writes `Allow: /llms.txt` for a file that returns HTTP 404. ## Start here - [Become an interface partner](https://www.yardi.com/company/become-an-interface-partner/): the access gate. Apply, sign a Data Exchange Agreement per interface type, develop, beta-test with a pilot client, release. Standard Interface partners must be at least two years old with three or more active Voyager clients; there is an annual per-interface fee. - [Standard interface options](https://www.yardi.com/services/interfaces/standard-interface-options/): the twelve documented Voyager interface families — Collections, Commercial, Construction, ILS & Guest Card, Maintenance, Master Data, Payables, Receivables, Renters Insurance, Revenue, Screening, Senior Living EHR/eMAR — with 450+ interface partners. MITS and OSCRE lineage claimed; no endpoints, WSDL or schema published. - [RentCafe API Terms of Use](https://resources.yardi.com/legal/rc-api-tou/): the most machine-adjacent public artifact Yardi serves. Its Schedule A names operations (getapartmentavailability, getfloorplans, getunitpricingdetails, getpropertydetails, getamenities, getofficehours, createlead, getavailableslots, createappointment) and it appears in a legal document rather than in documentation. ## Agent surface (this is the real one) - [Yardi Virtuoso Connector](https://claude.com/connectors/yardi-virtuoso): official first-party MCP server at https://mcp.virtuoso.ai. Read & Write. Published capabilities: portfolio performance, financial data and NOI comparison, work order management, invoice review and approval, quarterly business review, budget forecasting. Requires a licensed Virtuoso Enterprise tenancy; data access follows existing Yardi user permissions. - [OAuth protected-resource metadata](https://mcp.virtuoso.ai/.well-known/oauth-protected-resource): RFC 9728, anonymous. Scopes openid, profile, email, offline_access. - [OAuth authorization-server metadata](https://mcp.virtuoso.ai/.well-known/oauth-authorization-server): RFC 8414, anonymous. Authorization code + PKCE S256 + dynamic client registration. - tools/list is NOT anonymously introspectable — Cloudflare answers every anonymous POST with an HTML 403, so no tool names or input schemas are recorded anywhere in this repository. ## Callable today, without a contract - [Yardi Systems Status API](https://status.yardi.com/api): public, unauthenticated, 8 GET endpoints. 134 components in 16 product groups; seven of those groups carry an explicit `Canada` component (Voyager7s, Voyager8, Breeze, Elevate, Investor Portal, Resident Screening, Yardi EHR Interfaces). Canadian incidents and maintenance windows are named explicitly. - [Status page](https://status.yardi.com/) ## Specs and artifacts in this repository - openapi/yardi-canada-status-openapi.yml — the status API, DERIVED from Yardi's published endpoint list plus verified live responses. Yardi publishes no OpenAPI of its own. - overlays/yardi-canada-status-overlay.yaml — API Evangelist annotations over that spec. - mcp/yardi-canada-mcp.yml — the Virtuoso Connector profile. - mcp/yardi-canada-tool-crosswalk.yml — records that the MCP surface and the REST surface do not overlap at all (binding rate 0.0). - authentication/yardi-canada-authentication.yml — three coexisting regimes: OAuth 2.1 (MCP), contract-issued opaque token (RentCafe), none (status API). - scopes/yardi-canada-scopes.yml — the four published OAuth scopes; identity only, no product scopes. - well-known/yardi-canada-well-known.yml — every /.well-known/ probe across five hosts, hits and misses. - conformance/yardi-canada-conformance.yml — PCI, SSAE 18 with annual SOC 2 and biannual SOC 1, Sarbanes-Oxley, HIPAA, CSA STAR Level 2, FIPS 140-2; MCP authorization, RFC 8414, RFC 9728, PKCE, DCR; no RESO, no OData, no RFC 9457. - security/yardi-canada-trust-center.yml — the Cloud Security page and its named certifications. - security/yardi-canada-domain-security.yml — TLS/HSTS/DNS probes. - lifecycle/yardi-canada-lifecycle.yml — status page detail, no deprecation policy, no SLA. - changelog/yardi-canada-changelog.yml — seasonal "What's new in Yardi Breeze Premier" posts on the Canadian site; no API changelog. - conventions/yardi-canada-conventions.yml — what is knowable per surface; idempotency is genuinely absent. - data-model/yardi-canada-data-model.yml — the status entity graph, including how to resolve the Canadian slice. - packages/yardi-canada-packages.yml — zero official SDKs; two community clients, one of them a SOAP client that corroborates the interface style. - sandbox/yardi-canada-sandbox.yml — a real vendor sandbox that no developer can reach. - skills/ — three agent skills grounded in verified operationIds and verified OAuth metadata. ## Company - [Yardi Systems](https://www.yardi.com/) - [Yardi Breeze Canada](https://www.yardibreeze.ca/) — the live Canadian web presence; yardi.ca is a defensive registration that serves no content. - [Yardi Canada Ltd. 25-year retrospective](https://www.yardi.com/blog/global/yardi-canada-ltd-celebrates-25-years/37395.html) - [Cloud security](https://www.yardi.com/company/cloud-security/) - [Technical support](https://www.yardi.com/company/technical-support/) - [Client Central](https://clientcentral.yardi.com/) - [Privacy statement](https://resources.yardi.com/legal/privacy-statement/) - [Legal](https://www.yardi.com/company/legal/) ## What does not exist No public developer portal (developer./developers./api./docs. do not resolve on yardi.ca or yardi.com). No OpenAPI, WSDL, OData $metadata or GraphQL published by Yardi. No webhooks, no events, no AsyncAPI. No official SDKs, CLI or Postman collection. No RESO certification — the full RESO directory contains zero Yardi, Point2 or RentCafe entries, which is expected: Canadian listings move through CREA's DDF and REALTOR.ca. No security.txt, no vulnerability disclosure policy and no bug bounty anywhere on the estate.