Update RFI
update_rfiUpdate specific fields of an existing RFI in a Procore project. Provide project and RFI IDs to modify subject, assignees, due date, and other details, returning the updated object.
Instructions
Updates a specified RFI in a specified Project. Use this to update an existing RFI records (only the supplied fields are changed). Updates the specified RFI records and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > RFI. Endpoint: PATCH /rest/v1.0/projects/{project_id}/rfis/{id}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| id | Yes | URL path parameter — unique identifier of the RFI resource | |
| run_configurable_validations | No | Query string parameter — if true, validations are run for the corresponding Configurable Field Set. | |
| subject | No | JSON request body field — the Subject of the RFI | |
| reference | No | JSON request body field — the Reference of the RFI | |
| accepted | No | JSON request body field — the Accepted status of the RFI - closes or opens an RFI | |
| assignee_id | No | JSON request body field — the ID of the Assignee User. Note: not required if the creator is an admin and the RFI is a draft. *Only admin users can set this field DEPRECATED. Please use assignee_ids instead | |
| assignee_ids | No | JSON request body field — an array of IDs of the Assignees of the RFI *Only admin users can set this field **If this param is not provided, the assigned_id will be used instead | |
| required_assignee_ids | No | JSON request body field — an array of IDs of the Assignees that are required to respond to the RFI * Only admin users can set this field ** IDs must also be present in assignee_ids | |
| ball_in_court_id | No | JSON request body field — the ID of the Ball in Court of the RFI. This field is DEPRECATED as of March 31, 2019 and will no longer be supported as of October 1, 2019. | |
| draft | No | JSON request body field — the Draft status of the RFI (Can only be changed on draft RFIs) | |
| due_date | No | JSON request body field — the Due Date of the RFI *Only admin users can set this field | |
| received_from_login_information_id | No | JSON request body field — the ID of the Received From User of the RFI | |
| responsible_contractor_id | No | JSON request body field — the ID of the Responsible Contractor Vendor of the RFI | |
| distribution_ids | No | JSON request body field — an array of IDs of the Distributions of the RFI | |
| number | No | JSON request body field — the Number of the RFI *This field will be auto-populated if the RFI is not draft | |
| private | No | JSON request body field — the Private status of the RFI | |
| project_stage_id | No | JSON request body field — the ID of the Project Stage of the RFI *If Number By Stage is enabled in RFI settings, this will add the prefix of the project stage to the full number of the RFI. | |
| schedule_impact | No | JSON request body field — the Schedule Impact of the RFI | |
| cost_impact | No | JSON request body field — the Cost Impact of the RFI | |
| location_id | No | JSON request body field — the ID of the Location of the RFI | |
| drawing_number | No | JSON request body field — the Drawing Number of the RFI | |
| specification_section_id | No | JSON request body field — the ID of the Specification Section of the RFI | |
| cost_code_id | No | JSON request body field — the ID of the Cost Code of the RFI | |
| rfi_manager_id | No | JSON request body field — the ID of the RFI Manager User of the RFI *Only admin users (or standard users, if the project's configuration allows for it) can set this field | |
| question | No | JSON request body field — the Question of the RFI | |
| custom_textfield_1 | No | JSON request body field — the Custom Textfield 1 of the RFI | |
| custom_textfield_2 | No | JSON request body field — the Custom Textfield 2 of the RFI | |
| custom_field_%{custom_field_definition_id} | No | JSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ... |