manage bid packages, invites, and bids for a project via the autodesk buildingconnected api
domain: aps.autodesk.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an APS app and note BuildingConnected accepts only 3-legged OAuth (3LO) — server-to-server 2-legged tokens are not supported.
Work under the construction/buildingconnected/v2 base path (https://developer.api.autodesk.com/construction/buildingconnected/v2/), where each project represents one bidding phase of a construction project.
Create a bid package under a project with POST bid-packages — each package represents one scope of work with its own dates and publication state independent of the parent project.
List bid packages a user can access with GET bid-packages, and invite subcontractors/team members to a package.
Retrieve submitted bids with GET bids or a specific bid with GET bids/{bidId}, including bid form responses.
Manage project files/attachments and contacts tied to bids through the corresponding attachment and contact endpoints.
Known gotchas
BuildingConnected's data model cascades strictly project → bid package → bid; you cannot create a bid package without an existing (or accessible) parent project.
Only 3-legged tokens work, so this API can't be driven by a pure headless service account.
BuildingConnected and TradeTapp share the same API docs/surface but are separate products (TradeTapp is subcontractor prequalification) — confirm which product's data a given endpoint returns.
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?