> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.propexo.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.propexo.com/_mcp/server.

# Yardi QA Certification Guide

This guide outlines the full process for completing your Yardi QA certification call, including steps to take before, during, and after the call. It is written for teams going through Yardi’s QA regardless of whether the live integration uses **SOAP interfaces** or **Yardi REST** (your questionnaire and access checks should match the pathway you are certifying).

For where this step sits in the overall vendor timeline, see [Approval & QA Process](./approval-process).

---

## ❖ Before the Call

### Complete the Questionnaire

Yardi will send a pre-call questionnaire. One section will ask which Yardi methods your system uses.\
→ Use our documentation to identify the methods required for your integration based on the models you plan to sync. [This article from our Knowledge Base will help you identify which methods you will need access to.](https://kb.propexo.com/articles/9814036609-Understanding-Which-PMS-APIs-Propexo-uses)

### Review Plugin Version Info

Propexo provides API access to interface plugin version details.\
→ See: [**Propexo API Reference - Get Integration by ID**](https://docs.propexo.com/api-reference/configuration-ap-is/admin/get-integration-by-id#response.body.results.integration_interfaces.interface_name)

### Prepare QA Credentials

Yardi will provide a new set of QA credentials a few days before your scheduled call.

Once you receive the credentials:

1. **Create a new Yardi QA integration** in Propexo using the provided login.
2. **Run a data access check** to determine what those credentials give you access to.
   * This check should be done well ahead of the call to give you time to troubleshoot.
   * → See: [**Data Access Checks in Propexo**](https://kb.propexo.com/articles/1999278972-Using-the-Data-Access-panel-to-troubleshoot-your-integration)
3. **Confirm all expected models are accessible**. If any key models are missing, reach out to Yardi support and request an update to the integration's access.
4. Once access is confirmed, **enable the integration** and **run your initial sync** to ensure data is flowing correctly.

*Note: Running a sync before verifying access may result in partial data, so it's important to confirm first.*

---

## ❖ During the Call

### Product Demonstration (Optional)

The Yardi representative may ask for a brief product demo.\
*A demo is not required, and it’s okay if your product is still under development.*

# Interface Details and API View

The Yardi representative will likely ask you to show the version number of the Yardi interface(s) on your integration. You can retrieve this from the [**Get Integration By Id**](https://docs.propexo.com/api-reference/configuration-ap-is/admin/get-integration-by-id#response.body.results.integration_interfaces) API.
To present it, use Postman or a similar REST client to call that endpoint.

They may also ask you to view a specific record - for example:\
“Can you show me a resident with ID `t0012345` and the name `Bob Smith`?”\
Use your preferred tool to query the relevant Propexo API endpoint and display the response payload.

### Live Data Update

Yardi will make a live data change (e.g., updating a resident’s name) and ask you to confirm receipt on your end.

To do this:

* **Option 1**: Click the **“Sync Now”** button under the “Details” section in Propexo to sync all models.
* **Option 2**: [Trigger a **manual sync** with specific models and parameters, as documented in our API guide.](https://docs.propexo.com/api-reference/configuration-ap-is/admin/trigger-a-manual-sync-on-an-integration)

Kindly ask the Yardi rep to allow a few minutes for the sync to complete.\
Once done, confirm the specific change they asked you to verify.

---

## ❖ After the Call

### Approval & Follow-up

Most customers are approved for production use following the QA call.

If Yardi requests changes to your application or data flow:

* These are typically minor and handled asynchronously.
* You can respond with updated screenshots or documentation when ready.

### Deactivate the QA Integration

Once the call is complete:

* Disable or remove the QA integration from Propexo.
* Yardi will deactivate the QA credentials shortly afterward.