Yardi
Yardi Systems, Inc. (Goleta, California) builds the investment and property management software that residential, commercial, affordable housing, public housing, military housing, self-storage, coworking and senior living operators run as their system of record — Voyager, Breeze, RentCafe, Elevate, Investment Suite, Matrix, Kube and Virtuoso. It sits on the systems-of-record rung of the real estate value chain: the ledger and operating platform a landlord or asset manager runs on, not a listing portal and not a registry operator. 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 yardi.com, and the /platform/ and /platform/api/ paths previously catalogued here return HTTP 404. Real interfaces exist in volume, but only behind the Voyager Standard Interface Partnership Program (SIPP): 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 license fee per interface that is in some cases charged per transaction. A development sandbox is provided only after acceptance. The public "find an interface partner" page is a directory of 450+ already-accepted vendors across twelve interface categories, not documentation — its only calls to action are "Talk to sales" and "Contact us". Three public, machine-readable or anonymously readable surfaces do exist, and none of them is the Voyager API. Yardi ships a first-party MCP server, the Virtuoso Connector, whose OAuth 2.1 authorization contract is published anonymously on mcp.virtuoso.ai even though its tool list is not. status.yardi.com runs a full Atlassian Statuspage with an unauthenticated JSON API across 134 components in 16 product groups. And centershiftdevx.com, the legacy CenterShift developer site carried forward into Yardi Store, still serves genuine SWS2 endpoint documentation to anonymous readers — the only Yardi property that does. Every OpenAPI, JSON Schema, GraphQL schema, Postman collection and derived governance artifact in this repository was written by API Evangelist from Yardi's own interface naming and public partner documentation. Yardi publishes no OpenAPI, no WSDL, no OData $metadata and no machine-readable contract of any kind.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Yardi the way a machine reads it — 62 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Yardi scores 36.8/100 (thin), with a separate agent-readiness read of 26/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Yardi's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/yardi/"
title="Yardi on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/yardi.svg"
alt="Yardi Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/yardi/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/yardi/"
title="Yardi on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/yardi/card.svg"
alt="Yardi Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Yardi
Each block below is one kind of artifact we hold for Yardi. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Yardi Virtuoso Connector (MCP)
Yardi's first-party Model Context Protocol server, announced in early access on 2025-09-10 and described as generally available in Virtuoso Enterprise on 2026-06-16. Listed on t...
Yardi Store Web Services API (SWS2)
SOAP-based API for Yardi's self-storage management platform, formerly CenterShift. SWS2 provides tokenized authentication and store management methods for building custom applic...
Yardi Kube API
API and webhook integration for Yardi Kube, the coworking and flexible workspace management platform, covering member management, billing, space booking, access control and CRM ...
Yardi Voyager Commercial Data Interface
Voyager Standard Interface that exports commercial data from Yardi Voyager databases — property, unit, lease and rent roll information — built on the OSCRE standard with Yardi-s...
RentCafe API
The RentCafe marketing, leasing and resident-services API. Yardi's published RentCafe API Terms of Use names concrete operations in its Schedule A — getapartmentavailability, ge...
Yardi Senior Living EHR Interface
Voyager Standard Interface for Yardi's Electronic Health Records platform for senior living communities, supporting data exchange with pharmacy networks, laboratory systems and ...
Yardi Billing and Payments Interface
Operations for managing resident transactions, charges, payments, credits and billing data, accessed via the ItfResidentTransactions20 Voyager web service interface. Yardi publi...
Yardi Common Data Interface
Operations for retrieving shared property management data including properties, units, tenants and chart of accounts, accessed via the ItfCommonData Voyager web service interfac...
Yardi Job Cost Interface
Operations for job cost tracking, budgets and construction project financials, accessed via the ItfJobCost Voyager web service interface. Corresponds to the "Construction API" i...
Yardi Service Requests Interface
Operations for creating and managing maintenance work orders and service requests, accessed via the ItfServiceRequests Voyager web service interface. Corresponds to the "Mainten...
Yardi Vendor Invoicing Interface
Operations for vendor invoices, purchase orders and accounts payable transactions, accessed via the ItfVendorInvoice Voyager web service interface. Corresponds to the "Payables ...
Scroll within the panel for all 11 ·
Postman Collections 5
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONYardi Voyager Billing and Payments API
OPEN COLLECTIONYardi Voyager Billing and Payments Common Data API
OPEN COLLECTIONYardi Voyager Billing and Payments Job Cost API
OPEN COLLECTIONYardi Voyager Billing and Payments Service Requests API
OPEN COLLECTIONYardi Voyager Billing and Payments Vendor Invoicing API
OPEN COLLECTIONYardi Voyager API
OPEN COLLECTIONScroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Yardi MCP Server
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Yardi GraphQL API
Yardi is a property management and real estate investment platform. The API covers property records, lease management, resident/tenant data, financial transactions, maintenance ...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Yardi Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Yardi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Yardi Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Yardi Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Yardi API Rules
SPECTRALYardi API Rules
SPECTRALJSON Schema 25
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
BudgetDataResponse
JSON SCHEMAChartOfAccountsResponse
JSON SCHEMAGetBudgetDataRequest
JSON SCHEMAGetChartOfAccountsRequest
JSON SCHEMAGetJobCostDataRequest
JSON SCHEMAGetPropertyConfigurationsRequest
JSON SCHEMAGetResidentTransactionsByChargeDateRequest
JSON SCHEMAGetResidentTransactionsRequest
JSON SCHEMAGetServiceRequestsRequest
JSON SCHEMAGetTenantsRequest
JSON SCHEMAGetUnitInformationRequest
JSON SCHEMAGetVendorInvoicesRequest
JSON SCHEMAImportResidentTransactionsRequest
JSON SCHEMAImportResponse
JSON SCHEMAImportServiceRequestsRequest
JSON SCHEMAImportVendorInvoicesRequest
JSON SCHEMAJobCostDataResponse
JSON SCHEMAPropertyConfigurationsResponse
JSON SCHEMAServiceRequestsResponse
JSON SCHEMAYardi Tenant
JSON SCHEMATenantsResponse
JSON SCHEMAYardi Resident Transaction
JSON SCHEMATransactionResponse
JSON SCHEMAUnitInformationResponse
JSON SCHEMAVendorInvoicesResponse
JSON SCHEMAScroll within the panel for all 25 ·
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Yardi Structure
JSON STRUCTUREYardi Tenant Structure
JSON STRUCTUREExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Yardi Get Tenants Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Yardi — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/yardi · machine-readable index on apis.io
This is an independent, third-party profile of Yardi, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put 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.