Determine which integration method is appropriate: the Yardi Marketplace for pre-certified partner connectors, the Standard Interface Partnership for custom bidirectional data exchange, or the ETL tool for bulk import/export
For the Standard Interface Partnership, apply at yardi.com/company/become-an-interface-partner; your company must be at least two years old with at least three active Voyager clients, and a separate Data Exchange Agreement is required per interface type
For ETL-based integration, work with the Yardi account team to obtain ETL specifications; the ETL tool provides table- and field-level access for importing and exporting nearly all major Yardi data elements
For pre-built Marketplace integrations, activate the connector within Voyager's administration panel using credentials provided by the partner; no custom development is typically required
If using Yardi web services APIs directly, obtain the available WSDL or REST endpoint documentation from your Yardi account representative — API availability and endpoints vary by Voyager module and hosting environment
Test all data exchanges in Yardi's sandbox environment before production deployment; schema changes in Voyager upgrades can break custom integrations silently
Known gotchas
Yardi does not publish a self-serve public API; all integration paths require a formal relationship with Yardi or an approved partner — there is no free developer tier or public documentation portal
Voyager customizations and third-party add-ons can modify the underlying database schema; ETL mappings must be re-validated after any major Voyager upgrade
The Interface Partnership requirement of three active Voyager clients means early-stage or single-client integrators must pursue the ETL or Marketplace paths instead
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