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
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.
Areas: Accounting · Commercial Real Estate · Co-Working · Investment Management · MCP · Multifamily · Property Management · PropTech · Real Estate · Residential · Self Storage · Senior Living
Everything profiled for Yardi is published on APIs.io rather than in this repository. Start at the provider page — apis.io/providers/yardi/ — or go straight to one of the APIs or properties below.
- 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…
- 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…
- Yardi Kube API — API and webhook integration for Yardi Kube, the coworking and flexible workspace management platform, covering member management, billing, space booking,…
- 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…
- 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 —…
- 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,…
- Yardi Billing and Payments Interface — Operations for managing resident transactions, charges, payments, credits and billing data, accessed via the ItfResidentTransactions20 Voyager web service…
- Yardi Common Data Interface — Operations for retrieving shared property management data including properties, units, tenants and chart of accounts, accessed via the ItfCommonData Voyager…
- 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…
- Yardi Service Requests Interface — Operations for creating and managing maintenance work orders and service requests, accessed via the ItfServiceRequests Voyager web service interface.…
- Yardi Vendor Invoicing Interface — Operations for vendor invoices, purchase orders and accounts payable transactions, accessed via the ItfVendorInvoice Voyager web service interface.…
Each property below is a page on APIs.io carrying the machine-readable artifact and what it says.
GraphQL schemas.
Model Context Protocol servers that expose the API to agents.
Which operations an agent can call, which act, and which need a human in the loop.
The data models the API reads and writes.
- BudgetDataResponse
- ChartOfAccountsResponse
- GetBudgetDataRequest
- GetChartOfAccountsRequest
- GetJobCostDataRequest
- GetPropertyConfigurationsRequest
- GetResidentTransactionsByChargeDateRequest
- GetResidentTransactionsRequest
- GetServiceRequestsRequest
- GetTenantsRequest
- GetUnitInformationRequest
- GetVendorInvoicesRequest
- ImportResidentTransactionsRequest
- ImportResponse
- ImportServiceRequestsRequest
- ImportVendorInvoicesRequest
- JobCostDataResponse
- PropertyConfigurationsResponse
- ServiceRequestsResponse
- Yardi Tenant
- TenantsResponse
- Yardi Resident Transaction
- TransactionResponse
- UnitInformationResponse
- VendorInvoicesResponse
Data models expressed in JSON Structure.
Linked-data contexts for the provider's vocabulary.
The provider's domain terms, defined.
Example requests and responses.
Postman and Open Collection request collections.
- Yardi Voyager Billing and Payments API
- Yardi Voyager Billing and Payments Common Data API
- Yardi Voyager Billing and Payments Job Cost API
- Yardi Voyager Billing and Payments Service Requests API
- Yardi Voyager Billing and Payments Vendor Invoicing API
- Yardi Voyager API
- Yardi Voyager Billing and Payments API
- Yardi Voyager Billing and Payments Common Data API
- Yardi Voyager Billing and Payments Job Cost API
- Yardi Voyager Billing and Payments Service Requests API
- Yardi Voyager Billing and Payments Vendor Invoicing API
Spectral rulesets for the provider's contracts.
Authentication, trust centre, and vulnerability disclosure.
Published plans, tiers and prices.
Published request limits.
What the API costs to run, by operation.
Links to the company's own pages. This repository publishes no copy of their specifications — the canonical document is theirs and lives at the URLs below.
Kin Score 35.3 — thin · rubric 0.24.0 · scored 2026-10-17
| Facet | Score |
|---|---|
| Discoverability | 67.5 |
| Contract quality | 19.9 |
| Contract governance | 9.8 |
| Operational transparency | 23.7 |
| Developer ergonomics | 48.8 |
| Access clarity | 40.8 |
Agent readiness 23.9 — agent-aware
| Agent-readiness dimension | Result |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived (partial credit) |
| Reversibility Documented | — |
| MCP Server | documented (partial credit) |
| Auth Clarity | bearer (partial credit) |
| Idempotency | — |
| Error Semantics | — |
| OpenAPI Examples | — |
| Rate Limit Signal | derived (partial credit) |
| Event Surface Described | — |
| Agent Skills | — |
| Well Known Catalog | yes |
| Consent Identity | — |
| Agent Card | — |
| Dry Run Mode | — |
| Delegated Identity | — |
| Protected Resource Metadata | — |
| Dynamic Client Registration | — |
| Agentic Commerce | — |
Regulatory alignment 29.4 — Horizontal (data, software, accessibility, platform)
The rubric is published at github.com/api-evangelist/kin-score. The per-check breakdown behind these numbers — which checks were earned, partial or missed — along with score history and how this provider compares to its peers, is available at apis.io/providers/yardi/.
API Evangelist profiles a company's public API surface the way a developer would find it: the website, developer portal and documentation, the specifications it publishes, its public repositories, and its pricing, status and changelog pages. From that it derives the properties above — contracts split per API, workflows, schemas, collections, governance rules, plans and rate limits — and scores them against the published Kin Score rubric.
The artifacts are published on APIs.io, not in this repository. This repository is the public record for Yardi: the place to say something is wrong, missing or out of date, and to ask for a re-score or a removal.
- Something about this listing — a wrong description, a missing API, a stale artifact or a question about the rating: open an issue on this repository.
- A new API, or one that is not in the catalog yet — submit it on APIs.io.
- Anything else — the APIs.io inbox or info@apievangelist.com.