Yardi Voyager exposes data primarily via SOAP/XML web services; to access rent roll data, you must become an Interface Partner — apply at yardi.com/company/become-an-interface-partner and sign a per-interface agreement.
Each Yardi interface incurs an annual fee (reported as approximately $25,000 per interface as of recent disclosures); confirm current pricing directly with Yardi.
Obtain the WSDL URL, interface username, and interface password for the Commercial or Residential interface covering rent roll data; these differ from the Voyager application login.
Construct a SOAP envelope targeting the appropriate operation (e.g., GetRentRoll or a similarly named method in the Commercial API); parse the XML response which contains property, unit, lease, and charge data.
Parse returned fields including tenant name, unit ID, lease start/end, monthly rent, and balance; normalize to your internal schema and load into your data warehouse.
Schedule incremental exports (e.g., nightly) rather than full re-pulls; Yardi's SOAP interface does not have a native change-data-capture mechanism, so diff against your last snapshot.
Known gotchas
Yardi does not offer a public REST API for Voyager core data; the interface is SOAP-based and requires a signed partner agreement — any REST wrapper you find is a third-party abstraction.
Yardi environments are client-hosted or Yardi-hosted (Cloud); the WSDL URL and network access path differ between these and require coordination with the property management company's IT team.
Data returned varies by Voyager module and version; ensure you clarify whether the client runs Voyager 7S or a newer version, as schema differences affect field names and available operations.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp