Yardi Billing and Payments Interface
Operations for managing resident transactions, charges, payments, credits and billing data, accessed via the ItfResidentTransactions20 Voyager web service interface. Yardi publishes no specification for this interface; the OpenAPI in this repository was written by API Evangelist from Yardi's interface naming and public partner documentation, and has not been validated against a live endpoint. The Voyager service address is client-specific (https://{server}.yardi.com/{client}/webservices) and is issued only to accepted Interface Partnership Program vendors.
Yardi Billing and Payments Interface is one of 11 APIs that Yardi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Billing and Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.
This API exposes 4 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 20.0.
Requests are made against a single base URL, https://{server}.yardi.com/{clientUrl}/webservices.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Yardi Billing and Payments Interface declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (soapAuth).
By default, every request must be authenticated.
soapAuth— SOAP authentication using UserName, Password, and ServerName parameters passed within the SOAP request body. Credentials are provided by the Yardi Standard Int…
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.
Operations for managing resident transactions, charges, payments, credits, and billing data. Accessed via the ItfResidentTransactions20 web service interface.
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are GetResidentTransactionsByChargeDateRequest (10 properties), GetResidentTransactionsRequest (10 properties), GetBudgetDataRequest (10 properties), ImportResidentTransactionsRequest (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Yardi 10
Other APIs Yardi publishes across the network.
This is an independent, third-party profile of Yardi Billing and Payments Interface, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.