Overview
What is Yardi: Yardi provides software for the real estate industry. Its core platform, Yardi Voyager, handles property accounting, online rent payments, maintenance management, and property management automation across residential, commercial, affordable housing, senior living, and mixed portfolios.
How to integrate Yardi with Datagrid
With the Yardi integration, Datagrid agents pull Voyager records, process project files, and push structured records back. The integration syncs lease terms, rent-roll figures, contracts, work orders, and vendor payables depending on the licensed interface type.
Confirm Yardi interface access
Before Datagrid connects to Voyager, confirm the Voyager environment. Also confirm the interface user and interface scope.
Confirm your Yardi client runs Voyager 7S with the required plug-in versions: Interfaces PIv22, Common Data PIv19, and Service Requests PIv15.
Create an interface user in Voyager linked to a security group for the specific interface type, with Read or Read/Write access.
Enter the property code or list code, then select Interface User on the Privileges tab to grant web service access.
Provide Datagrid with the Voyager URL, interface username, password, database name, and server name.
In Datagrid, add the Yardi integration and enter the supplied credentials to establish the integration.
A typical Datagrid Yardi integration configuration uses these fields:
{
"voyager_url": "https://your-voyager-url",
"interface_username": "yardi_interface_user",
"password": "provided_by_yardi_client",
"database_name": "yardi_database_name",
"server_name": "yardi_server_name",
"property_or_list_code": "property_code_or_list_code",
"interface_type": "licensed_interface_type",
"access_mode": "Read or Read/Write"
}Authenticate the Yardi integration
Yardi Voyager SOAP interfaces use an interface username and password passed per request, alongside the database and server name. Report credential changes to the connecting vendor. Full API access requires a completed Yardi Interface Partnership agreement. It also requires a Data Exchange Agreement per interface type, as described by the Yardi partner program.
Datagrid can store the per-request authentication values in this shape:
{
"request_context": {
"voyager_url": "https://your-voyager-url",
"database_name": "yardi_database_name",
"server_name": "yardi_server_name"
},
"credentials": {
"interface_username": "yardi_interface_user",
"password": "provided_by_yardi_client"
},
"access": {
"property_or_list_code": "property_code_or_list_code",
"access_mode": "Read or Read/Write"
}
}Configure Yardi data sync details
Voyager exports property, unit, lease, and rent-roll data. Construction, maintenance, payables, and renters insurance interfaces support bidirectional sync. Voyager uses a polling/pull model with no native webhooks, so Datagrid pipelines run on configurable polling intervals with manual Sync Now triggers.
A Datagrid sync configuration can separate read flows from bidirectional flows:
{
"sync_mode": "polling",
"polling_interval": "configurable",
"manual_trigger": "Sync Now",
"read_flows": [
"property",
"unit",
"lease",
"rent_roll"
],
"bidirectional_flows": [
"contracts",
"work_orders",
"vendor_payables",
"renters_insurance"
]
}Once access, credentials, and polling are set, Datagrid agents can run lease, financial, compliance, and construction workflows.
Why use Yardi with Datagrid
Integrating Yardi with Datagrid gives property and construction teams an execution layer for work that usually sits between Voyager exports, lease files, spreadsheets, and reporting systems.
Automated lease abstraction: Datagrid agents read scanned lease PDFs using OCR trained on legal terminology. They extract renewal deadlines and escalation triggers, then prepare structured data for Yardi without rekeying.
Multi-entity consolidation: Agents pull financial data from Yardi and map chart-of-account differences across entities to merge records into a single live dataset. This replaces month-end manual consolidation.
Voyager SOAP handling built in: Datagrid manages Yardi's SOAP/WSDL payloads and XML parsing, so your team avoids building SOAP client libraries from scratch.
Cross-platform orchestration: Datagrid integrates Yardi with non-Yardi systems and handles multi-source data from Yardi plus corporate ERP ledgers and warehouses for unified reporting.
Automated compliance triggers: Datagrid's Automation Agent starts compliance verification when vendor or tenant changes occur in Yardi, then flags exceptions and generates audit trails.
What you can build with Yardi Datagrid integration
Use Yardi data as the starting point for agents that extract lease terms, consolidate financials, verify compliance, and analyze budget movement. Common builds include:
Lease abstraction pipeline: Build an agent that reads incoming lease documents, extracts key terms, renewal deadlines, and option windows, then writes structured records into Yardi. See agents for lease abstraction.
Financial close consolidation: Connect Yardi alongside corporate ERP systems to pull GL data continuously, normalize coded values, and produce a live consolidated dataset. This replaces the month-end cycle where accounting teams pull data from Yardi and scattered spreadsheets.
Compliance and insurance verification: Build an agent that extracts coverage details, policy numbers, and effective dates from incoming certificates. It compares them against documented requirements in Yardi and flags exceptions with audit trails.
Budget variance analysis: Ingest GL data directly from Yardi without reformatting charts of accounts, then run automated variance analysis. This replaces spreadsheet workflows that require exporting trial balances and rebuilding pivots.
Resources and documentation
Yardi partner program covers eligibility, onboarding, and licensing.
Yardi partner directory lists supported API types and approved vendors.
RentCafe terms covers the publicly documented Yardi API and best-practice guidance.
Yardi Data Connect describes the Voyager to Power BI integration product.
Frequently asked questions
Can Datagrid connect to the Yardi API?
Yes. Yardi Voyager provides SOAP-based web services defined via WSDL. These services cover billing, common data, service requests, vendor invoicing, job cost, and commercial data export. Full specifications require a completed partner agreement.
How does a third-party vendor get API access to Yardi?
Access follows a five-step process: submit the Interface Partnership Program application, complete a Data Exchange Agreement per interface type, develop your application, beta-test with a pilot client, then move to general release.
What credentials does Datagrid need?
Datagrid needs the Voyager URL, interface username, password, database name, and server name. Report any credential changes to the connecting vendor.
Is Datagrid an approved Yardi partner?
Yes. Yardi's official partner directory lists Datagrid as Toric/Datagrid, an approved vendor for the Construction API, which covers contracts, job info, and change orders.
Similar integrations
Oracle Netsuite: Consolidate financials and run cross-ERP reporting by combining Yardi property accounting with corporate ERP ledgers.
QuickBooks: Sync transactional data between Yardi and SMB bookkeeping systems for small-portfolio accounting workflows.
Sage Intacct: Produce corporate financial reporting and consolidation across multi-entity property portfolios alongside Yardi datasets.
Snowflake: Receive replicated Yardi data for enterprise analytics, cross-platform joins, and AI-driven reporting pipelines.
Procore: Sync project budgets, change orders, and job-cost details with Yardi for unified construction financials and job-cost reporting.