Yardi Canada

Yardi Canada Ltd. is the Canadian subsidiary of Yardi Systems, Inc. (Goleta, California), opened in Mississauga in 1998 and now headquartered in Toronto with regional offices in Saskatoon and Vancouver and roughly 500 staff. It sells, implements and supports the Yardi property and investment management stack in Canada — Voyager, Breeze Premier, RentCafe, Home IQ, Matrix and Pulse — across residential, commercial, affordable, senior living and investment portfolios, and its Canadian footprint grew by acquisition: Point2 Technologies in Saskatoon in 2010, an EnerNOC division in Vancouver in 2016, and Planimetron in Toronto in 2022. It sits on the systems-of-record rung of the value chain rather than the listing or land-registration rung — it is the ledger and operating platform a landlord or asset manager runs on, not a portal like REALTOR.ca and not a registry operator like Teranet. Its API posture, stated honestly, is licensed-access-only and partner-gated. There is no public developer portal: developer., developers., api. and docs. hosts do not resolve on either yardi.ca or yardi.com, and the primary Canadian domain yardi.ca — registered to Yardi Systems, Inc. since 2003 — resolves to 104.156.161.80 but serves no web content at all (TCP 443 and 80 both time out). Real interfaces exist, but only behind the Interface Partnership Program: an application, a signed Data Exchange Agreement per interface type, a company at least two years old with three or more active Voyager clients, and an annual per-interface fee. RESO is absent entirely — Yardi appears nowhere in the RESO certification directory — which is the expected result for a Canadian property management vendor, because Canadian residential listings move through CREA's DDF and REALTOR.ca rather than through RESO-certified MLS endpoints. Two public, machine-readable surfaces do exist and neither of them is REST. Yardi ships a first-party MCP server — the Yardi Virtuoso Connector, listed on the Anthropic connector directory and served from mcp.virtuoso.ai — whose OAuth 2.1 authorization contract (RFC 8414 and RFC 9728 metadata, PKCE, dynamic client registration) is published anonymously even though its tool list is not. And status.yardi.com runs a full Atlassian Statuspage with a public JSON API across 134 components in 16 product groups, seven of which carry an explicit Canada component — the only anonymous, machine-readable signal of Yardi Canada's production service health.

Yardi Canada publishes 1 API on the APIs.io network: Yardi Systems Status API. Tagged areas include Real Estate, Canada, Property Management, Rentals, and Commercial Real Estate.

Yardi Canada’s developer surface includes documentation, authentication, changelog, support, legal docs, engineering blog, product news, and 29 more developer resources.

51.5/100 developing ▬ flat Agent 62/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
4 APIs 1 MCP Servers
Real EstateCanadaProperty ManagementRentalsCommercial Real EstatePropTechMultifamilyAffordable HousingSenior LivingInvestment ManagementTenancyPaymentsMCPAI

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 51.5/100 · developing
Contract Quality 13.5 / 25
Developer Ergonomics 8.3 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 4.8 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 62/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 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/yardi-canada: 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.

Yardi Voyager Standard Interfaces

The documented family of Voyager web-service interfaces that Yardi Canada clients and their vendors integrate against — Collections, Commercial, Construction, Internet Listing S...

RentCafe API

The RentCafe marketing, leasing and resident-services API, used by Yardi Canada's multifamily clients and their vendors. Yardi's published RentCafe API Terms of Use names concre...

Yardi Virtuoso Connector (MCP)

Yardi's first-party Model Context Protocol server, announced in early access on 2025-09-10 and described as available now in Virtuoso Enterprise on 2026-06-16. Listed on the Ant...

Yardi Systems Status API

The only Yardi API that can be called today without a contract. It is the Atlassian Statuspage v2 REST API hosted on Yardi's own status host, with the endpoint list published by...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Security Posture 3

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

Yardi Canada Authentication

oauth2/opaque-token/none · 4 schemes

SECURITY

Yardi Canada Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Yardi Canada Trust Center

SOC 2 (annual), SOC 1 (biannual), SSAE 18, PCI, HIPAA, Sarbanes-Oxley, CSA STAR Level 2, FIPS 140-2 (key management)

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Yardi Canada Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Yardi Canada Agentic Access

8 operations

8 operations · 0 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 9

The organization behind the API

Scroll for all 9

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: yardi-canada
url: https://raw.githubusercontent.com/api-evangelist/yardi-canada/refs/heads/main/apis.yml
name: Yardi Canada
kind: company
description: 'Yardi Canada Ltd. is the Canadian subsidiary of Yardi Systems, Inc. (Goleta, California), opened in Mississauga
  in 1998 and now headquartered in Toronto with regional offices in Saskatoon and Vancouver and roughly 500 staff. It sells,
  implements and supports the Yardi property and investment management stack in Canada — Voyager, Breeze Premier, RentCafe,
  Home IQ, Matrix and Pulse — across residential, commercial, affordable, senior living and investment portfolios, and its
  Canadian footprint grew by acquisition: Point2 Technologies in Saskatoon in 2010, an EnerNOC division in Vancouver in 2016,
  and Planimetron in Toronto in 2022. It sits on the systems-of-record rung of the value chain rather than the listing or
  land-registration rung — it is the ledger and operating platform a landlord or asset manager runs on, not a portal like
  REALTOR.ca and not a registry operator like Teranet. Its API posture, stated honestly, is licensed-access-only and partner-gated.
  There is no public developer portal: developer., developers., api. and docs. hosts do not resolve on either yardi.ca or
  yardi.com, and the primary Canadian domain yardi.ca — registered to Yardi Systems, Inc. since 2003 — resolves to 104.156.161.80
  but serves no web content at all (TCP 443 and 80 both time out). Real interfaces exist, but only behind the Interface Partnership
  Program: an application, a signed Data Exchange Agreement per interface type, a company at least two years old with three
  or more active Voyager clients, and an annual per-interface fee. RESO is absent entirely — Yardi appears nowhere in the
  RESO certification directory — which is the expected result for a Canadian property management vendor, because Canadian
  residential listings move through CREA''s DDF and REALTOR.ca rather than through RESO-certified MLS endpoints. Two public,
  machine-readable surfaces do exist and neither of them is REST. Yardi ships a first-party MCP server — the Yardi Virtuoso
  Connector, listed on the Anthropic connector directory and served from mcp.virtuoso.ai — whose OAuth 2.1 authorization contract
  (RFC 8414 and RFC 9728 metadata, PKCE, dynamic client registration) is published anonymously even though its tool list is
  not. And status.yardi.com runs a full Atlassian Statuspage with a public JSON API across 134 components in 16 product groups,
  seven of which carry an explicit Canada component — the only anonymous, machine-readable signal of Yardi Canada''s production
  service health.'
image: https://www.yardi.com/wp-content/themes/cmw-standard-v2-theme/images/icons/apple-touch-icon-152x152.png
tags:
- Real Estate
- Canada
- Property Management
- Rentals
- Commercial Real Estate
- PropTech
- Multifamily
- Affordable Housing
- Senior Living
- Investment Management
- Tenancy
- Payments
- MCP
- AI
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.19'
apis:
- aid: yardi-canada:yardi-voyager-standard-interfaces
  name: Yardi Voyager Standard Interfaces
  description: The documented family of Voyager web-service interfaces that Yardi Canada clients and their vendors integrate
    against — Collections, Commercial, Construction, Internet Listing Service (ILS) and Guest Card, Maintenance, Master Data,
    Payables, Receivables, Renters Insurance, Revenue, Screening, and Senior Living EHR/eMAR. Several are described by Yardi
    as MITS-based or MITS-compliant; the Commercial interface is described as built on the OSCRE standard. The contracting
    party is Yardi Systems, Inc.; Yardi Canada Ltd. is the Canadian delivery and support entity. No base URL, endpoint list,
    WSDL, OpenAPI or OData $metadata document is published anywhere public — access is granted only after acceptance into
    the Interface Partnership Program and execution of a Data Exchange Agreement for each interface type, and only to companies
    at least two years old with three or more active Voyager clients, against an annual per-interface fee.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/groq.png
  humanURL: https://www.yardi.com/services/interfaces/standard-interface-options/
  tags:
  - Property Management
  - Commercial Real Estate
  - Maintenance
  - Accounting
  - Screening
  - Listings
  - MITS
  - OSCRE
  properties:
  - type: Documentation
    url: https://www.yardi.com/services/interfaces/standard-interface-options/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  - type: Partners
    url: https://www.yardi.com/company/become-an-interface-partner/
- aid: yardi-canada:rentcafe-api
  name: RentCafe API
  description: The RentCafe marketing, leasing and resident-services API, used by Yardi Canada's multifamily clients and their
    vendors. Yardi's published RentCafe API Terms of Use names concrete operations in its Schedule A — getapartmentavailability,
    getfloorplans, getunitpricingdetails, getpropertydetails, getamenities, getofficehours, createlead, getavailableslots
    and createappointment — and states that use "is by way of that certain RentCafe API Access Agreement between you and Yardi
    Systems, Inc." Access is restricted to vendors serving "Common Clients" (entities that are clients of both Yardi and the
    vendor), credentials are described only as an access token, and the vendor may not pass Common Client Data to third parties.
    No base URL, reference documentation, OpenAPI document or self-serve signup is published; https://www.rentcafe.com/api/
    no longer serves documentation.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/groq.png
  humanURL: https://resources.yardi.com/legal/rc-api-tou/
  tags:
  - Multifamily
  - Rentals
  - Leasing
  - Residents
  - Payments
  - Marketing
  properties:
  - type: TermsOfService
    url: https://resources.yardi.com/legal/rc-api-tou/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  - type: Documentation
    url: https://www.yardi.com/products/rentcafe/
- aid: yardi-canada:yardi-virtuoso-connector-mcp
  name: Yardi Virtuoso Connector (MCP)
  description: 'Yardi''s first-party Model Context Protocol server, announced in early access on 2025-09-10 and described
    as available now in Virtuoso Enterprise on 2026-06-16. Listed on the Anthropic connector directory as Read & Write in
    the Financial services category, supported across Claude web, desktop, mobile, Claude Code and the Claude API. Published
    capabilities are portfolio performance analysis across properties and markets, financial data including Net Operating
    Income comparisons, work order management and tracking, invoice review and approval workflows, quarterly business review
    support, and budget forecasting. Authorization is real and anonymously discoverable — RFC 9728 protected-resource metadata
    and RFC 8414 authorization-server metadata on mcp.virtuoso.ai publish an OAuth 2.1 authorization-code flow with PKCE S256,
    refresh tokens and dynamic client registration, with the scopes openid, profile, email and offline_access. Those scopes
    carry identity only: Yardi states data access follows the caller''s existing Yardi user permissions, so a Yardi Canada
    client''s tenancy roles are the real boundary. The tool list is not anonymously introspectable — every unauthenticated
    JSON-RPC POST is answered with an HTML 403 by Cloudflare — and the connector''s technical documentation returns HTTP 401,
    so no tool names or input schemas are asserted in this profile. Access requires a licensed, configured Virtuoso Enterprise
    tenancy; there is no trial and no developer sandbox.'
  image: https://www.yardi.com/wp-content/themes/cmw-standard-v2-theme/images/icons/apple-touch-icon-152x152.png
  humanURL: https://claude.com/connectors/yardi-virtuoso
  baseURL: https://mcp.virtuoso.ai
  tags:
  - MCP
  - AI
  - Agents
  - Property Management
  - Investment Management
  - Maintenance
  - Accounting
  properties:
  - type: MCPServer
    url: mcp/yardi-canada-mcp.yml
  - type: ToolCrosswalk
    url: mcp/yardi-canada-tool-crosswalk.yml
  - type: WellKnown
    url: well-known/yardi-canada-well-known.yml
  - type: OAuthScopes
    url: scopes/yardi-canada-scopes.yml
  - type: Authentication
    url: authentication/yardi-canada-authentication.yml
  - type: Documentation
    url: https://help.virtuoso.ai/en/articles/13679727-yardi-virtuoso-mcp-technical-documentation-guide
  - type: About
    url: https://www.yardi.com/news/press-releases/yardi-adds-virtuoso-connector-for-claude-to-its-ai-platform/
- aid: yardi-canada:yardi-systems-status-api
  name: Yardi Systems Status API
  description: 'The only Yardi API that can be called today without a contract. It is the Atlassian Statuspage v2 REST API
    hosted on Yardi''s own status host, with the endpoint list published by Yardi at https://status.yardi.com/api: eight unauthenticated
    GET endpoints covering the rolled-up page status, the full component tree, incidents (all and unresolved) and scheduled
    maintenances (all, upcoming and active). The page carries 134 components across 16 product groups — Voyager7s, Voyager8,
    Breeze, RentCafe and its ANZ/UK/Middle East siblings, CommercialCafe, Elevate, Investor Portal, Kube, Payment Processing,
    Relief Suite, Resident Screening, VendorCafe and Yardi EHR Interfaces — and seven of those groups expose an explicit Canada
    component, which makes this the only public, machine-readable read on Yardi Canada''s production service health. Canadian
    incidents and maintenance windows are named outright, for example "Issue impacting Yardi Voyager users in the Canada region"
    and "Maintenance - Canada Region - Thursday April 23 - 11:00pm EDT". The OpenAPI in this repository was derived by API
    Evangelist from Yardi''s published endpoint list plus verified live 200 responses; Yardi publishes no OpenAPI of its own.'
  image: https://www.yardi.com/wp-content/themes/cmw-standard-v2-theme/images/icons/apple-touch-icon-152x152.png
  humanURL: https://status.yardi.com/api
  baseURL: https://status.yardi.com/api/v2
  tags:
  - Status
  - Monitoring
  - Incidents
  - Maintenance
  - Canada
  - Property Management
  properties:
  - type: OpenAPI
    url: openapi/yardi-canada-status-openapi.yml
  - type: Overlay
    url: overlays/yardi-canada-status-overlay.yaml
  - type: DataModel
    url: data-model/yardi-canada-data-model.yml
  - type: Conventions
    url: conventions/yardi-canada-conventions.yml
  - type: AgenticAccess
    url: agentic-access/yardi-canada-agentic-access.yml
  - type: Documentation
    url: https://status.yardi.com/api
  - type: StatusPage
    url: https://status.yardi.com/
common:
- type: AgenticAccess
  url: agentic-access/yardi-canada-agentic-access.yml
- type: DomainSecurity
  url: security/yardi-canada-domain-security.yml
- type: Website
  url: https://www.yardibreeze.ca/
- type: Website
  url: https://www.yardi.com/
- type: About
  url: https://www.yardi.com/blog/global/yardi-canada-ltd-celebrates-25-years/37395.html
- type: Partners
  url: https://www.yardi.com/company/become-an-interface-partner/
- type: Documentation
  url: https://www.yardi.com/services/interfaces/standard-interface-options/
- type: TermsOfService
  url: https://resources.yardi.com/legal/rc-api-tou/
- type: Solutions
  url: https://info.yardi.com/asset-management-software-for-canada
- type: GitHubOrganization
  url: https://github.com/YardiSystems
- type: LinkedIn
  url: https://www.linkedin.com/company/yardi
- type: MCPServer
  url: mcp/yardi-canada-mcp.yml
- type: ToolCrosswalk
  url: mcp/yardi-canada-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Authentication
  url: authentication/yardi-canada-authentication.yml
- type: OAuthScopes
  url: scopes/yardi-canada-scopes.yml
- type: WellKnown
  url: well-known/yardi-canada-well-known.yml
- type: Conformance
  url: conformance/yardi-canada-conformance.yml
- type: Compliance
  url: https://www.yardi.com/company/cloud-security/
- type: TrustCenter
  url: security/yardi-canada-trust-center.yml
- type: Lifecycle
  url: lifecycle/yardi-canada-lifecycle.yml
- type: StatusPage
  url: https://status.yardi.com/
- type: ChangeLog
  url: changelog/yardi-canada-changelog.yml
- type: Conventions
  url: conventions/yardi-canada-conventions.yml
- type: DataModel
  url: data-model/yardi-canada-data-model.yml
- type: Packages
  url: packages/yardi-canada-packages.yml
- type: LLMsTxt
  url: llms/yardi-canada-llms.txt
- type: Overlay
  url: overlays/yardi-canada-status-overlay.yaml
- type: Support
  url: https://www.yardi.com/company/technical-support/
- type: Login
  url: https://clientcentral.yardi.com/
- type: PrivacyPolicy
  url: https://resources.yardi.com/legal/privacy-statement/
- type: Legal
  url: https://www.yardi.com/company/legal/
- type: Blog
  url: https://www.yardibreeze.ca/blog/
- type: BlogRSS
  url: https://www.yardibreeze.ca/feed/
- type: News
  url: https://www.yardi.com/news/
- type: Careers
  url: https://www.yardi.com/careers/
- type: ContactUs
  url: https://www.yardi.com/company/contact-us/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com