create, transition, and comment on rfis in an autodesk construction cloud project via the acc rfis 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
Authenticate with a 3-legged token carrying data:read (for GET) and data:write (for POST/PATCH), since RFI actions are attributed to the acting ACC user.
List RFIs with GET https://developer.api.autodesk.com/construction/rfis/v2/projects/{projectId}/rfis, or POST rfis/rfi-search for filtered/paginated queries (search uses POST because filters live in the request body).
Fetch valid statuses/custom fields first via GET rfi-types, then create an RFI with POST .../rfis (subject, question, assignee, dueDate, etc.).
Advance an RFI through its workflow with PATCH .../rfis/{rfiId}, and add discussion with POST .../rfis/{rfiId}/comments.
Retrieve a single RFI's full detail, including the official response, with GET .../rfis/{rfiId}.
Confirm the acting user's permissions first with GET .../rfis/v2/projects/{projectId}/users/me before attempting writes.
Known gotchas
Autodesk is consolidating legacy /construction/rfis/ endpoints into routes that work for both ACC and BIM 360 projects — check current base path before hardcoding /construction/.
Status transitions are workflow-constrained; a PATCH that skips a required intermediate state (e.g. draft straight to closed) is rejected.
rfi-search is a POST despite being read-only, since filter criteria go in the body, not the query string — don't assume GET.
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?