Update Witness Statement
update_witness_statementUpdate an existing witness statement's details, such as statement text, date received, or attachments, in Procore Incidents.
Instructions
Updates the specified Witness Statement. 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/witness_statements/{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 — witness Statement ID | |
| incident_id | No | Query string parameter — unique identifier of the incident | |
| statement | No | JSON request body field — the account of the event by the witness in rich text form. | |
| date_received | No | JSON request body field — date that the Witness Statement was received. This assumes the dates provided are in the project timezone. | |
| witness_id | No | JSON request body field — unique identifier of the witness | |
| upload_uuids | No | JSON request body field — array of uploaded file UUIDs. | |
| 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 | |
| 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 ... | |
| recording | No | JSON request body field — the recording for this Incidents operation |