Submit and track association architectural requests with file attachments via the Buildium Open API
domain: developer.buildium.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with x-buildium-client-id and x-buildium-client-secret headers
Call GET /v1/associations/ownershipaccounts/architecturalrequests to list architectural (ARC) requests
Use the corresponding POST to create a new request, and GET /{architecturalRequestId} to retrieve one
Call POST /v1/associations/ownershipaccounts/architecturalrequests/{architecturalRequestId}/files/uploadrequests to attach supporting documents
Call POST /v1/associations/ownershipaccounts/architecturalrequests/{architecturalRequestId}/files/{fileId}/downloadrequests to generate a download link for an attached file
Known gotchas
File attachment is a two-step flow: initiate an upload, then confirm/reference the returned fileId; posting binary data directly to the request record will not work
Downloading an attached file requires POSTing a separate download request (not issuing a GET against the file resource) to obtain the download link
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?