Create RFI
create_rfiCreates a new RFI in a Procore project using subject, manager, and question. Returns the created RFI with its ID or an error status for invalid requests.
Instructions
Creates a new RFI in a specified Project. Pass the record's fields as top-level arguments — they are nested under "rfi" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Creates the RFI and returns it with its new id (HTTP 201); calling it again creates another record. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id, subject, rfi_manager_id, question. Procore API: Project Management > RFI. Endpoint: POST /rest/v1.0/projects/{project_id}/rfis
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| draft | No | JSON request body field — the Draft status 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 **When creating a new revision of an RFI, if not provided, it will inherit the number from the source RFI. | |
| private | No | JSON request body field — the Private status of the RFI | |
| subject | Yes | JSON request body field — the Subject of the RFI | |
| due_date | No | JSON request body field — the Due Date of the RFI *Only admin users can set this field | |
| question | Yes | JSON request body field — the Question of the RFI | |
| revision | No | JSON request body field — revision Number *This field is required only when creating a new revision of an RFI. | |
| reference | No | JSON request body field — the Reference of the RFI | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| assignee_id | No | JSON request body field — the ID of the Assignee User. *Only admin users can set this field DEPRECATED. Please use assignee_ids instead | |
| 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 | |
| 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 | |
| cost_code_id | No | JSON request body field — the ID of the Cost Code of the RFI | |
| drawing_number | No | JSON request body field — the Drawing Number of the RFI | |
| rfi_manager_id | Yes | 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 | |
| schedule_impact | No | JSON request body field — the Schedule Impact of the RFI | |
| distribution_ids | No | JSON request body field — an array of IDs of the Distributions 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. **This field is not needed when c... | |
| 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 | |
| source_rfi_header_id | No | JSON request body field — the ID of The Root RFI Revision *This field is required only when creating a new revision of an RFI. | |
| 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 | |
| specification_section_id | No | JSON request body field — the ID of the Specification Section of the RFI | |
| responsible_contractor_id | No | JSON request body field — the ID of the Responsible Contractor Vendor of the RFI | |
| run_configurable_validations | No | Query string parameter — if true, validations are run for the corresponding Configurable Field Set. | |
| received_from_login_information_id | No | JSON request body field — the ID of the Received From User 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 ... |