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 Buildings API

Resources providing access to buildings.

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

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

This API exposes 13 operations across 9 paths, and defines 21 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 9 paths 21 schemas 2 DELETE7 GET2 POST2 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 Buildings 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 9 paths, the API surfaces 13 operations — 2 DELETE, 7 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Buildings 13

Resources providing access to buildings.

GET
/buildings
Retrieve all buildings
getBuildings 11 params → 200400401403
POST
/buildings
Create a building
createBuilding body → 201400401403
POST
/buildings/bulk
Create buildings in bulk
createContacts body → 201400401403
PUT
/buildings/customfields
Update a building custom fields (BETA)
updateBuilding body → 200400401403404
GET
/buildings/{buildingID}
Retrieve a building
getBuilding 2 params → 200400401403404
PUT
/buildings/{buildingID}
Update a building
updateBuildingUsingPUT_1 1 param body → 200400401403404
DELETE
/buildings/{buildingID}
Delete a building (BETA)
deleteBuilding 1 param → 204400401403404
GET
/buildings/{buildingID}/conversations
Retrieve all building conversations
getBuildingConversations 7 params → 200400401403404
GET
/buildings/{buildingID}/conversations/{conversationID}
Retrieve a building conversation
getBuildingConversation 2 params → 200400401403404
DELETE
/buildings/{buildingID}/conversations/{conversationID}
Delete a building conversation (BETA)
deleteBuildingConversation 2 params → 204400401403404
GET
/buildings/{buildingID}/managementfees
Retrieves all the management fee rules of a building. (BETA)
getBuildingManagementFee 1 param → 200400401403404
GET
/buildings/{buildingID}/managers
Retrieves all the property managers of a building
getBuildingManagers 1 param → 200400401403404
GET
/buildings/{buildingID}/notes
Retrieves all the notes of a building.
getBuildingNotes 1 param → 200400401403404

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are Building (56 properties), SaveBuilding (47 properties), UpdateBuilding (45 properties), Marketing (24 properties). Each schema is shown below with its type and property counts.

Note
object
9 properties
UpdateBuilding
object
UpdateBuilding
45 properties 6 required
RESTAPIBulkErrorResponse
object
3 properties
PropertyManager
object
PropertyManager
5 properties
Marketing
object
Marketing Information
24 properties
RESTAPIBulkSuccessResponse
object
1 property
Address
object
Address
6 properties
SaveBuilding
object
SaveBuilding
47 properties 8 required
ManagementSettings
object
Property management information
6 properties
RESTAPIError
object
2 properties
Amenity
object
Amenity
4 properties
ManagementFee
object
Management Fee
7 properties
ErrorResponse
object
3 properties
Comment
object
Comment
6 properties
ResponseEntity
object
2 properties
Conversation
object
Conversation
10 properties
CustomFieldSet
object
Custom field set for Request
2 properties 2 required
SaveAddress
object
Address.
6 properties 1 required
CustomField
object
Custom field.
4 properties
SaveCustomField
object
Custom field for Request
2 properties 2 required
Building
object
Building
56 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

propertyware-buildings-api-openapi.yml Raw ↑

Other APIs Propertyware publishes across the network.

Propertyware Accounting API
Propertyware Bills 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
Propertyware Vendors API
Where this information came from

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