How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Yardi Service Requests Interface

Operations for creating and managing maintenance work orders and service requests, accessed via the ItfServiceRequests Voyager web service interface. Corresponds to the "Maintenance API" interface category on Yardi's partner directory. 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.

Yardi Service Requests Interface is one of 11 APIs that Yardi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Service Requests, Maintenance, and Work Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 4 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.

2 operations 2 paths 4 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
20.0
Server
https://{server}.yardi.com/{clientUrl}/webservices
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Yardi Service Requests 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 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Service Requests 2

Operations for creating and managing maintenance work orders and service requests. Accessed via the ItfServiceRequests web service interface.

POST
/ItfServiceRequests.asmx/GetServiceRequests_Login
Yardi Get service requests
getServiceRequestsLogin body → 200401500
POST
/ItfServiceRequests.asmx/ImportServiceRequests_Login
Yardi Import service requests
importServiceRequestsLogin body → 200401500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are GetServiceRequestsRequest (10 properties), ImportServiceRequestsRequest (9 properties), ImportResponse (2 properties), ServiceRequestsResponse (1 property). Each schema is shown below with its type and property counts.

ServiceRequestsResponse
object
SOAP response containing service request and work order data.
1 property
ImportServiceRequestsRequest
object
SOAP request for creating or updating service requests in Voyager.
9 properties 9 required
ImportResponse
object
SOAP response confirming successful import of data.
2 properties
GetServiceRequestsRequest
object
SOAP request for retrieving service requests and work orders.
10 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yardi-service-requests-api-openapi.yml Raw ↑

Other APIs Yardi publishes across the network.

Yardi Virtuoso Connector (MCP)
Yardi Store Web Services API (SWS2)
Yardi Kube API
Yardi Voyager Commercial Data Interface
RentCafe API
Yardi Senior Living EHR Interface
Yardi Billing and Payments Interface
Yardi Common Data Interface
Yardi Job Cost Interface
Yardi Vendor Invoicing Interface
Where this information came from

This is an independent, third-party profile of Yardi Service Requests 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.