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

Propertyware Work orders API

Resources providing access to work orders.

Propertyware Work orders API is one of 14 APIs that Propertyware publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Work Orders. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 13 operations across 10 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.propertyware.com/pw/api/rest/v1.

13 operations 10 paths 17 schemas 2 DELETE4 GET4 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://app.propertyware.com/pw/api/
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Propertyware Work orders API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-propertyware-client-id (clientId). An API key is passed in the header as x-propertyware-client-secret (clientSecret). An API key is passed in the header as x-propertyware-system-id (organizationId). By default, every request must be authenticated.

Paths & Operations 13

Across 10 paths, the API surfaces 13 operations — 2 DELETE, 4 GET, 4 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Work orders 13

Resources providing access to work orders.

GET
/workorders
Retrieve all work orders
getWorkOrders 13 params → 200400401403
POST
/workorders
Create a work order
createWorkOrder body → 201400401403
POST
/workorders/bulk
Create work orders in bulk
createWorkOrders body → 201400401403
PUT
/workorders/closeworkorder/{workOrderID}
Close a Workorder (BETA)
closeWorkOrder 1 param body → 200400401403404
PUT
/workorders/customfields
Update a workorder custom fields (BETA)
updateWorkOrder body → 200400401403404
DELETE
/workorders/{workOrderID}
Delete a Work Order (BETA)
deleteWorkOrder 1 param → 204400401403404
GET
/workorders/{workOrderID}/tasks/{taskID}
Retrieve a work order task
getWorkOrderTask 2 params → 200400401403404
DELETE
/workorders/{workOrderID}/tasks/{taskID}
Delete a work order task (BETA)
deleteWorkOrderTask 2 params → 204400401403404
GET
/workorders/{workOrderId}
Retrieve a work order
getWorkOrder 2 params → 200400401403404
GET
/workorders/{workOrderId}/tasks
Retrieve all work order tasks
getWorkOrderTasks 8 params → 200400401403404
POST
/workorders/{workOrderId}/tasks
Create a task to workOrder
createWorkOrderTask 1 param body → 201400401403404
PUT
/workorders/{workOrderId}/tasks/{taskId}
Update a task in workOrder
updateWorkOrderTask 2 params body → 200400401403404
POST
/workorders/{workOrderId}/tasks/{taskId}/comments
Add Comments to task for a workOrder
addWorkOrderTaskComments 2 params body → 201400401403404

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are WorkOrder (39 properties), SaveWorkOrder (21 properties), Task (13 properties), BasicVendor (12 properties). Each schema is shown below with its type and property counts.

SaveWorkOrder
object
Work Order for Request
21 properties 1 required
CloseWorkOrder
object
5 properties 1 required
RESTAPIBulkErrorResponse
object
3 properties
BasicVendor
object
12 properties
RESTAPIBulkSuccessResponse
object
1 property
Collection_long_
object
WorkOrder
object
Work Order
39 properties
RESTAPIError
object
2 properties
SaveComment
object
Comment for Request
1 property 1 required
SaveWorkOrderTask
object
Work Order for Request
7 properties 1 required
Task
object
Task
13 properties
ErrorResponse
object
3 properties
ResponseEntity
object
2 properties
CustomFieldSet
object
Custom field set for Request
2 properties 2 required
CustomField
object
Custom field.
4 properties
TimeCardEntry
object
TimeCardEntry
8 properties 1 required
SaveCustomField
object
Custom field for Request
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

propertyware-work-orders-api-openapi.yml Raw ↑

Other APIs Propertyware publishes across the network.

Propertyware Accounting API
Propertyware Bills API
Propertyware Buildings API
Propertyware Contacts API
Propertyware Custom field definitions API
Propertyware Documents API
Propertyware Health check API
Propertyware Inspections API
Propertyware Leases API
Propertyware Portfolios API
Propertyware Prospects API
Propertyware Units API
Where this information came from

This is an independent, third-party profile of Propertyware Work orders API, 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.