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

# Integration Credentials

These fields apply to **Yardi REST** integrations in Propexo. Yardi supplies most of the values you need as you move through their vendor program; timing and handoffs are described in [Approval & QA Process](../approval-process).

For Voyager **SOAP** interface credentials (company ID, database, interface-specific setup), see [Integration Credentials (SOAP)](../soap/credentials).

For end-to-end setup in Propexo, see the Knowledge Base guide [Creating a Yardi REST integration](https://kb.propexo.com/articles/9876080047-Creating-a-Yardi-REST-integration).

## What you need from the customer or Yardi

* **Interface username and password** — Must come from the customer or directly from Yardi during the QA process. Propexo cannot generate these.
* **Interface entity** — Yardi provides this. Each interface entity has an equivalent **API token**; use the pairing Yardi gives you for that entity.

Other environment-specific values (for example URLs or identifiers Yardi issues for sandbox vs production) are typically delivered while you complete QA with Yardi. If anything is missing, confirm with Yardi Interfaces Support or your customer using the same QA thread.

Enter the values in the Propexo UI when creating or editing the Yardi REST integration.