Generate API credentials (client ID and secret) in the Buildium administration console under Settings > API; the Buildium API follows REST conventions with JSON bodies.
POST to the work orders endpoint (documented at developer.buildium.com) with required fields: title, property ID, unit ID, and priority level; optionally include a description and vendor assignment.
Capture the returned work order ID and store it in your system for subsequent status polling or updates.
PATCH or PUT the work order resource with updated status values (e.g., in-progress, completed) as field technicians report progress; include the work order ID in the path.
Retrieve open work orders for a property by GET-ing the work orders collection filtered by propertyId and status to build a maintenance dashboard.
Use the Buildium webhook configuration (if available for your plan) to receive real-time status change events rather than polling.
Known gotchas
The Buildium API version is v1; always prefix calls with /v1/ and check the changelog at developer.buildium.com for breaking changes before upgrades.
Vendor assignment via API requires that the vendor record already exists in Buildium; the API will reject a vendor ID that has not been pre-created.
Work order attachments (photos, invoices) are handled through a separate file-upload endpoint and must be linked to the work order after creation.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp