Update Incident
update_incidentUpdate an existing Procore incident by specifying the project ID and incident ID. Modify fields such as title, status, assignees, and more. Returns the updated incident.
Instructions
Updates the specified Incident. Use this to update an existing Incidents (only the supplied fields are changed). Updates the specified Incidents and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Incidents. Endpoint: PATCH /rest/v1.0/projects/{project_id}/incidents/{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 Incidents resource | |
| run_configurable_validations | No | Query string parameter — whether or not Configurable validations from the Incident/Injury Configurable Field Set should be run (default: false). See (https://developers.procore.com/reference/configurable-field-sets#list-pr... | |
| description | No | JSON request body field — description of the Incident | |
| event_date | No | JSON request body field — iso8601 datetime of Incident occurrence. If time is unknown, send in the date at 0:00 project time converted to UTC. | |
| type_id | No | JSON request body field — the ID of the Incident Type. Defaults to the company's General type if not provided. The type must be active. | |
| custom_status_id | No | JSON request body field — the ID of the Custom Status. Mutually exclusive with the status field — setting one sets the other. Not updatable if the Incident has a workflows instance. | |
| assignee_ids | No | JSON request body field — an array of Login Information IDs to assign to the Incident. Assignees gain visibility into the Incident and its related records. Not updatable if the Incident has a workflows instance. | |
| distribution_member_ids | No | JSON request body field — an Array of the IDs of the Distribution Members (Not updatable if an incident has a workflows instance) | |
| private | No | JSON request body field — indicates whether an Incident is private | |
| recordable | No | JSON request body field — indicates whether an Incident is recordable | |
| status | No | JSON request body field — status (Not updatable if an incident has a workflows instance) | |
| time_unknown | No | JSON request body field — indicates that the time of the Incident occurrence is unknown | |
| title | No | JSON request body field — incident Title | |
| contributing_behavior_id | No | JSON request body field — the ID of a Contributing Behavior | |
| contributing_condition_id | No | JSON request body field — the ID of a Contributing Condition | |
| hazard_id | No | JSON request body field — unique identifier of the hazard | |
| location_id | No | JSON request body field — the ID of a Location | |
| environmentals | No | JSON request body field — associated Environmentals to create | |
| injuries | No | JSON request body field — associated Injuries to create | |
| near_misses | No | JSON request body field — associated Near Misses to create | |
| property_damages | No | JSON request body field — associated Property Damages to create | |
| witness_statements_attributes | No | JSON request body field — associated Witness Statement to create | |
| upload_uuids | No | JSON request body field — array of uploaded file UUIDs. | |
| 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 ... | |
| drawing_revision_ids | No | JSON request body field — drawing Revisions to attach to the response | |
| file_version_ids | No | JSON request body field — file Versions to attach to the response | |
| form_ids | No | JSON request body field — forms to attach to the response | |
| image_ids | No | JSON request body field — images to attach to the response |