> This page is for version v2 (default).
> For other versions, use one of these documentation indexes:
> - v2 (default): https://autodesk-poc.ferndocs.com/v2/llms.txt
> - v1: https://autodesk-poc.ferndocs.com/v1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://autodesk-poc.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://autodesk-poc.ferndocs.com/_mcp/server.

# Forma RFIs

The RFIs (Requests for Information) API enables you to programmatically manage the lifecycle of RFIs in Forma. RFIs are formal questions raised during a construction project that require clarification from stakeholders. This API allows you to create, update, transition, and track RFIs and their associated data.

For more information about RFIs in the product, see the [RFIs help documentation](https://help.autodesk.com/view/BUILD/ENU/?guid=RFIs_Overview).

## Key Features

* Create, update, and retrieve RFIs
* Transition RFIs between workflow statuses (e.g., draft → open → submitted)
* Create and update responses with optional attachments
* Retrieve and validate custom identifiers
* Create, update, and retrieve custom attributes
* Retrieve user permissions and workflow details
* Add and retrieve comments
* Retrieve attachments associated with an RFI

## Typical Workflow

A typical RFI workflow includes the following steps:

1. Create an RFI in `draft` status.
2. Transition the RFI to `open` by assigning users.
3. Assigned users submit responses.
4. The RFI is transitioned to `submitted` (usually by the manager).
5. An official response is optionally added.
6. The RFI is closed.

Use the `permittedActions` block in the RFI and workflow responses to determine valid transitions and which users can be assigned or respond at each stage.

For details, see the [RFI Transitions](https://aps.autodesk.com/en/docs/acc/v1/tutorials/rfi-transitions/) tutorial.

## Limitations and Notes

The RFIs API does not currently support:

* Batch creation or update of RFIs
* Retrieving activity logs
* Adding or inviting users to a project
* Updating advanced project settings
* Modifying user roles or permissions
* Deleting RFIs, responses, or attachments
* Deleting custom attributes
* Webhook events

## Best Practices and Common Issues

* Available actions and status transitions vary based on the user’s role and current RFI state. Always refer to the `permittedActions` object.
* Only users with a manager workflow role can be assigned to RFIs in certain statuses.
* Transitions that require attributes (such as assignees) will fail if those fields are missing.

---

*Imported from the Autodesk Platform Services documentation: [https://aps.autodesk.com/en/docs/acc/v1/overview/field-guide/rfis](https://aps.autodesk.com/en/docs/acc/v1/overview/field-guide/rfis).*