Yardi website screenshot

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.

Yardi publishes 5 APIs on the APIs.io network, including Billing and Payments Interface, Common Data Interface, Job Cost Interface, and 2 more. Tagged areas include Accounting, Commercial Real Estate, Coworking, Investment Management, and MCP.

The Yardi catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Yardi’s developer surface includes documentation, getting-started guide, authentication, legal docs, support, training material, engineering blog, and 15 more developer resources.

56.9/100 strong ▼ -6.0 Agent 45/100 agent ready Full breakdown ↓
scored 2026-07-28 · rubric v0.6
AccessEnterpriseApproval
11 APIs 1 MCP Servers
AccountingCommercial Real EstateCoworkingInvestment ManagementMCPMultifamilyProperty ManagementPropTechReal EstateResidentialSelf StorageSenior Living

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 56.9/100 · strong
Contract Quality 14.8 / 25
Developer Ergonomics 10.0 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 5.5 / 13
Governance 7.0 / 12
Discoverability 7.6 / 10
Agent readiness — 45/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
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 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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: 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 11

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 for all 11

Postman Collections 5

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

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Yardi Voyager API

OPEN COLLECTION

MCP Servers 1

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

mcp.virtuoso.ai

MCP SERVER

GraphQL 1

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

GRAPHQL

Pricing Plans 1

Published pricing tiers and plan structures.

Yardi Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Yardi Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Yardi Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Yardi Context

0 classes · 28 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Yardi API Rules

5 rules · 3 warnings 2 info

SPECTRAL

Yardi API Rules

10 rules · 2 errors 8 warnings

SPECTRAL

JSON Schema 25

Standalone JSON Schema definitions for this provider's data models.

BudgetDataResponse

1 properties

JSON SCHEMA

ChartOfAccountsResponse

1 properties

JSON SCHEMA

GetBudgetDataRequest

10 properties

JSON SCHEMA

GetChartOfAccountsRequest

8 properties

JSON SCHEMA

GetJobCostDataRequest

9 properties

JSON SCHEMA

GetPropertyConfigurationsRequest

8 properties

JSON SCHEMA

GetResidentTransactionsRequest

10 properties

JSON SCHEMA

GetServiceRequestsRequest

10 properties

JSON SCHEMA

GetTenantsRequest

8 properties

JSON SCHEMA

GetUnitInformationRequest

8 properties

JSON SCHEMA

GetVendorInvoicesRequest

10 properties

JSON SCHEMA

ImportResidentTransactionsRequest

9 properties

JSON SCHEMA

ImportResponse

2 properties

JSON SCHEMA

ImportServiceRequestsRequest

9 properties

JSON SCHEMA

ImportVendorInvoicesRequest

9 properties

JSON SCHEMA

JobCostDataResponse

1 properties

JSON SCHEMA

PropertyConfigurationsResponse

1 properties

JSON SCHEMA

ServiceRequestsResponse

1 properties

JSON SCHEMA

Yardi Tenant

14 properties

JSON SCHEMA

TenantsResponse

1 properties

JSON SCHEMA

Yardi Resident Transaction

12 properties

JSON SCHEMA

TransactionResponse

1 properties

JSON SCHEMA

UnitInformationResponse

1 properties

JSON SCHEMA

VendorInvoicesResponse

1 properties

JSON SCHEMA

Scroll for all 25

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Yardi Structure

0 properties

JSON STRUCTURE

Yardi Tenant Structure

0 properties

JSON STRUCTURE

Examples 1

Example request and response payloads for these APIs.

Yardi Get Tenants Example

2 fields

EXAMPLE

Security Posture 2

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

Yardi Authentication

http · 1 scheme

SECURITY

Yardi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

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

Yardi Agentic Access

13 operations · 13 acting

13 operations · 13 acting

AGENTIC

Resources

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

Source (apis.yml)

apis.yml Raw ↑
aid: yardi
name: Yardi
description: '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.'
accessModel:
  pricing: enterprise
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Enterprise · Partner-gated (SIPP application, Data Exchange Agreement per interface, annual per-interface fee, 3+
    active Voyager clients required)
  confidence: high
  source:
  - https://www.yardi.com/company/become-an-interface-partner/
  - https://www.yardi.com/company/find-an-interface-partner/
  generated: '2026-07-28'
  method: researched
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/yardi.png
url: https://raw.githubusercontent.com/api-evangelist/yardi/refs/heads/main/apis.yml
created: '2025-01-01'
modified: '2026-07-28'
specificationVersion: '0.19'
apis:
- aid: yardi: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
    generally available in Virtuoso Enterprise on 2026-06-16. Listed on the Anthropic connector directory as Read & Write
    in the Financial services category. 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. Those scopes carry identity
    only; Yardi states data access follows the caller's existing Yardi user permissions. The tool list is not anonymously
    introspectable and the technical documentation returns HTTP 401, so no tool names or input schemas are asserted here.
    Access requires a licensed, configured Virtuoso Enterprise tenancy — there is no trial and no developer sandbox. This
    is the most agent-ready surface Yardi operates.
  humanURL: https://claude.com/connectors/yardi-virtuoso
  baseURL: https://mcp.virtuoso.ai
  tags:
  - MCP
  - AI
  - Agents
  - Property Management
  - Investment Management
  properties:
  - type: About
    url: https://www.yardi.com/news/press-releases/yardi-adds-virtuoso-connector-for-claude-to-its-ai-platform/
  - type: WellKnown
    url: https://mcp.virtuoso.ai/.well-known/oauth-protected-resource
- aid: yardi:yardi-store-web-services-api
  name: Yardi Store Web Services API (SWS2)
  description: SOAP-based API for Yardi's self-storage management platform, formerly CenterShift. SWS2 provides tokenized
    authentication and store management methods for building custom applications and websites against Yardi Store Enterprise
    and Store Advantage. Notable as the only Yardi interface with genuine developer documentation readable by an anonymous
    visitor — the legacy centershiftdevx.com site publishes an endpoint list, an authentication overview and support contacts.
    The documentation has not been updated since 2017 and the site is not linked from yardi.com.
  humanURL: https://centershiftdevx.com/
  tags:
  - Reservations
  - Self Storage
  - SOAP
  - Store Management
  properties:
  - type: Documentation
    url: https://centershiftdevx.com/2015/01/22/sws2-api-documentation/
  - type: Reference
    url: https://centershiftdevx.com/2017/01/23/end-points/
  - type: GettingStarted
    url: https://centershiftdevx.com/2017/04/16/overview-using-yardi-store-web-services-sws/
  - type: Support
    url: https://centershiftdevx.com/2011/06/20/contacting-centershift/
- aid: yardi:yardi-kube-api
  name: Yardi Kube API
  description: API and webhook integration for Yardi Kube, the coworking and flexible workspace management platform, covering
    member management, billing, space booking, access control and CRM integrations. The integrations page is public and the
    api. yardikube.com host resolves, but no reference documentation, endpoint list or machine-readable contract is published
    — access is arranged through Yardi Kube account management.
  humanURL: https://www.yardikube.com/integrations-api/
  baseURL: https://api.yardikube.com
  tags:
  - Booking
  - Coworking
  - Flexible Workspace
  - Webhooks
  properties:
  - type: Documentation
    url: https://www.yardikube.com/integrations-api/
- aid: yardi:yardi-voyager-commercial-data-api
  name: Yardi Voyager Commercial Data Interface
  description: 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-specific extensions. Announced by press release; no
    endpoint list, WSDL or specification is published publicly. Access requires acceptance into the Interface Partnership
    Program and a Data Exchange Agreement for the Commercial interface type.
  humanURL: https://www.yardi.com/company/find-an-interface-partner/
  tags:
  - Commercial
  - Data Export
  - Leasing
  - OSCRE
  properties:
  - type: About
    url: https://www.yardi.com/news/press-releases/yardi-adds-commercial-data-interface-to-voyager-standard-interface-partnership-program/
  - type: Documentation
    url: https://www.yardi.com/company/find-an-interface-partner/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
- aid: yardi:yardi-rentcafe-api
  name: RentCafe API
  description: 'The RentCafe marketing, leasing and resident-services API. 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), and the vendor may not pass Common Client Data
    to third parties. The Terms of Use is the only public artifact: no base URL, reference documentation, OpenAPI document
    or self-serve signup is published, api.rentcafe.com and www.rentcafe.com/api/ both return HTTP 403 to anonymous clients.'
  humanURL: https://resources.yardi.com/legal/rc-api-tou/
  tags:
  - Applications
  - Multifamily
  - Payments
  - Portal
  - Residents
  properties:
  - type: TermsOfService
    url: https://resources.yardi.com/legal/rc-api-tou/
  - type: Documentation
    url: https://www.yardi.com/product/rentcafe-resident-portal/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
- aid: yardi:yardi-senior-living-ehr-api
  name: Yardi Senior Living EHR Interface
  description: Voyager Standard Interface for Yardi's Electronic Health Records platform for senior living communities, supporting
    data exchange with pharmacy networks, laboratory systems and other healthcare partners through standardized interfaces
    including NCPDP 10.6 SCRIPT. Listed as the "Senior Living EHR/eMAR" interface category on the partner directory. No endpoint
    documentation is published; access is partner-gated.
  humanURL: https://www.yardi.com/product/ehr/
  tags:
  - EHR
  - Healthcare
  - Pharmacy
  - Senior Living
  properties:
  - type: Documentation
    url: https://www.yardi.com/product/ehr/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
- aid: yardi:yardi-billing-and-payments-api
  name: Yardi Billing and Payments Interface
  description: Operations for managing resident transactions, charges, payments, credits and billing data, accessed via the
    ItfResidentTransactions20 Voyager web service interface. Yardi publishes no specification for this interface; the OpenAPI
    in this repository was written by API Evangelist from Yardi's interface naming and public partner documentation, and has
    not been validated against a live endpoint. The Voyager service address is client-specific (https://{server}.yardi.com/{client}/webservices)
    and is issued only to accepted Interface Partnership Program vendors.
  humanURL: https://www.yardi.com/suite/voyager-suite/
  tags:
  - Billing and Payments
  properties:
  - type: OpenAPI
    url: openapi/yardi-billing-and-payments-api-openapi.yml
  - type: Documentation
    url: https://www.yardi.com/company/find-an-interface-partner/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  x-provenance:
    provider_published: false
    derived_by: API Evangelist
    method: derived
    basis: Yardi Voyager Standard Interface naming and public partner documentation
    validated_against_live_endpoint: false
    artifacts:
    - openapi/yardi-billing-and-payments-api-openapi.yml
    - postman/yardi-billing-and-payments-api.postman_collection.json
- aid: yardi:yardi-common-data-api
  name: Yardi Common Data Interface
  description: Operations for retrieving shared property management data including properties, units, tenants and chart of
    accounts, accessed via the ItfCommonData Voyager web service interface. Yardi publishes no specification for this interface;
    the OpenAPI in this repository was written by API Evangelist from Yardi's interface naming and public partner documentation,
    and has not been validated against a live endpoint.
  humanURL: https://www.yardi.com/suite/voyager-suite/
  tags:
  - Common Data
  properties:
  - type: OpenAPI
    url: openapi/yardi-common-data-api-openapi.yml
  - type: Documentation
    url: https://www.yardi.com/company/find-an-interface-partner/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  x-provenance:
    provider_published: false
    derived_by: API Evangelist
    method: derived
    basis: Yardi Voyager Standard Interface naming and public partner documentation
    validated_against_live_endpoint: false
    artifacts:
    - openapi/yardi-common-data-api-openapi.yml
    - postman/yardi-common-data-api.postman_collection.json
- aid: yardi:yardi-job-cost-api
  name: Yardi Job Cost Interface
  description: Operations for job cost tracking, budgets and construction project financials, accessed via the ItfJobCost
    Voyager web service interface. Corresponds to the "Construction API" interface category on Yardi's partner directory.
    Yardi publishes no specification for this interface; the OpenAPI in this repository was written by API Evangelist from
    Yardi's interface naming and public partner documentation, and has not been validated against a live endpoint.
  humanURL: https://www.yardi.com/suite/voyager-suite/
  tags:
  - Job Cost
  properties:
  - type: OpenAPI
    url: openapi/yardi-job-cost-api-openapi.yml
  - type: Documentation
    url: https://www.yardi.com/company/find-an-interface-partner/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  x-provenance:
    provider_published: false
    derived_by: API Evangelist
    method: derived
    basis: Yardi Voyager Standard Interface naming and public partner documentation
    validated_against_live_endpoint: false
    artifacts:
    - openapi/yardi-job-cost-api-openapi.yml
    - postman/yardi-job-cost-api.postman_collection.json
- aid: yardi:yardi-service-requests-api
  name: Yardi Service Requests Interface
  description: Operations for creating and managing maintenance work orders and service requests, accessed via the ItfServiceRequests
    Voyager web service interface. Corresponds to the "Maintenance API" interface category on Yardi's partner directory. Yardi
    publishes no specification for this interface; the OpenAPI in this repository was written by API Evangelist from Yardi's
    interface naming and public partner documentation, and has not been validated against a live endpoint.
  humanURL: https://www.yardi.com/suite/voyager-suite/
  tags:
  - Service Requests
  - Maintenance
  - Work Orders
  properties:
  - type: OpenAPI
    url: openapi/yardi-service-requests-api-openapi.yml
  - type: Documentation
    url: https://www.yardi.com/company/find-an-interface-partner/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  x-provenance:
    provider_published: false
    derived_by: API Evangelist
    method: derived
    basis: Yardi Voyager Standard Interface naming and public partner documentation
    validated_against_live_endpoint: false
    artifacts:
    - openapi/yardi-service-requests-api-openapi.yml
    - postman/yardi-service-requests-api.postman_collection.json
- aid: yardi:yardi-vendor-invoicing-api
  name: Yardi Vendor Invoicing Interface
  description: Operations for vendor invoices, purchase orders and accounts payable transactions, accessed via the ItfVendorInvoice
    Voyager web service interface. Corresponds to the "Payables API" interface category on Yardi's partner directory. Yardi
    publishes no specification for this interface; the OpenAPI in this repository was written by API Evangelist from Yardi's
    interface naming and public partner documentation, and has not been validated against a live endpoint.
  humanURL: https://www.yardi.com/suite/voyager-suite/
  tags:
  - Vendor Invoicing
  - Payables
  properties:
  - type: OpenAPI
    url: openapi/yardi-vendor-invoicing-api-openapi.yml
  - type: Documentation
    url: https://www.yardi.com/company/find-an-interface-partner/
  - type: GettingStarted
    url: https://www.yardi.com/company/become-an-interface-partner/
  x-provenance:
    provider_published: false
    derived_by: API Evangelist
    method: derived
    basis: Yardi Voyager Standard Interface naming and public partner documentation
    validated_against_live_endpoint: false
    artifacts:
    - openapi/yardi-vendor-invoicing-api-openapi.yml
    - postman/yardi-vendor-invoicing-api.postman_collection.json
x-provenance:
  summary: Yardi publishes no machine-readable API contract of any kind — no OpenAPI, no WSDL, no OData $metadata, no AsyncAPI.
    Every specification and derived artifact in this repository was authored by API Evangelist from Yardi's public interface
    naming and partner documentation. None of it should be credited to Yardi as provider-published, and none of it has been
    validated against a live Yardi endpoint.
  provider_published_artifacts:
  - https://resources.yardi.com/legal/rc-api-tou/
  - https://centershiftdevx.com/2017/01/23/end-points/
  - https://status.yardi.com/api
  - https://mcp.virtuoso.ai/.well-known/oauth-protected-resource
  ae_derived_artifacts:
  - openapi/
  - json-schema/
  - json-structure/
  - json-ld/
  - graphql/
  - postman/
  - collections/
  - examples/
  - agentic-access/
  - authentication/
  - rules/
  - vocabulary/
  - finops/
  - plans/
  - rate-limits/
  verified: '2026-07-28'
common:
- type: Website
  url: https://www.yardi.com
- type: Documentation
  url: https://www.yardi.com/company/find-an-interface-partner/
- type: GettingStarted
  url: https://www.yardi.com/company/become-an-interface-partner/
- type: Partners
  url: https://www.yardi.com/company/find-an-interface-partner/
- type: StatusPage
  url: https://status.yardi.com/
- type: StatusAPI
  url: https://status.yardi.com/api
- type: MCPServer
  url: https://mcp.virtuoso.ai
- type: WellKnown
  url: https://mcp.virtuoso.ai/.well-known/oauth-protected-resource
- type: AgenticAccess
  url: agentic-access/yardi-agentic-access.yml
- type: DomainSecurity
  url: security/yardi-domain-security.yml
- type: Authentication
  url: authentication/yardi-authentication.yml
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/yardi/overview
- type: Compliance
  url: https://www.yardi.com/company/cloud-security/
- type: LinkedIn
  url: https://www.linkedin.com/company/yardi-systems
- type: GitHubOrganization
  url: https://github.com/YardiSystems
- type: PrivacyPolicy
  url: https://resources.yardi.com/legal/privacy-statement/
- type: Legal
  url: https://www.yardi.com/company/legal/
- type: Support
  url: https://www.yardi.com/company/technical-support/
- type: Login
  url: https://clientcentral.yardi.com/
- type: Training
  url: https://www.yardi.com/company/training/
- type: Integrations
  url: https://www.yardi.com/product/marketplace/
- type: Blog
  url: https://www.yardi.com/blog/
- type: News
  url: https://www.yardi.com/news/
notes: "Corrected 2026-07-28 after a fresh review of Yardi's actual public posture.\n\nRemoved as fabricated — these paths\
  \ were catalogued but do not exist:\n  - https://www.yardi.com/platform/                     (HTTP 404, was \"Portal\")\n\
  \  - https://www.yardi.com/platform/api/                 (HTTP 404, was \"Documentation\"\n                            \
  \                             on 5 entries and \"Developer\n                                                         Resources\"\
  \ in common)\n  - https://www.yardi.com/platform/api/authentication/  (HTTP 404, was \"Authentication\"\n              \
  \                                           on 5 entries)\n  - https://www.yardi.com/platform/api/maintenance/     (HTTP\
  \ 404)\n  - https://www.yardi.com/platform/api/investment/      (redirects to a marketing page,\n                      \
  \                                   not API documentation)\n  - baseURL https://api.yardi.com                       (does\
  \ not resolve; was asserted\n                                                         on 8 entries, plus invented\n    \
  \                                                     /maintenance and /investment\n                                   \
  \                      paths)\n  - https://www.yardi.com/products/voyager/             (HTTP 404; real page is\n       \
  \                                                  /suite/voyager-suite/)\n  - https://www.yardi.com/support/          \
  \            (HTTP 404)\n  - https://www.yardi.com/contact-us/                   (HTTP 403)\n  - https://www.yardi.com/about-us/legal/terms-of-use/\
  \  (HTTP 403)\n  - https://www.rentcafe.com/api/                       (HTTP 403, no longer serves docs)\n  - baseURL https://api.rentcafe.com\
  \                    (HTTP 403)\n\nRemoved as unevidenced APIs — marketing products with no evidence of a named,\nseparately\
  \ documented API:\n  - Yardi Maintenance IQ API   (maintenance is an interface category, covered by the\n              \
  \                  Service Requests interface entry)\n  - Yardi Investment Manager API\n\naccessModel corrected from onboarding:\
  \ self-serve to onboarding: approval. There is\nno signup of any kind; the previous \"Signup\" property pointed at a partner\n\
  application form and has been removed.\n\nThe GitHubOrganization link is retained for completeness but carries no API value\
  \ —\ngithub.com/YardiSystems holds 13 repositories, all forks of third-party projects\n(quill, FileSaver.js, websocketd,\
  \ bolt.diy, rrule). Yardi publishes no first-party\nAPI artifacts there.\n\nSee also all/yardi-canada, which was researched\
  \ to this standard on 2026-07-26, and\nall/yardi-propware.\n"
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
tags:
- Accounting
- Commercial Real Estate
- Coworking
- Investment Management
- MCP
- Multifamily
- Property Management
- PropTech
- Real Estate
- Residential
- Self Storage
- Senior Living