POST /rest/v1.0/projects/{project_id}/incidents/witness_statements
Creates a Witness Statement.
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
project_id |
Integer | Yes |
Unique identifier for the project. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Procore-Company-Id |
Integer | Yes |
Unique company identifier associated with the Procore User Account. |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
witness_statement |
Object | Yes | |
witness_statement.file_version_ids[] |
Array | No |
File Versions to attach to the response |
witness_statement.form_ids[] |
Array | No |
Forms to attach to the response |
witness_statement.statement |
String | No |
The account of the event by the witness in rich text form. |
witness_statement.upload_uuids[] |
Array | No |
Array of uploaded file UUIDs. |
witness_statement.image_ids[] |
Array | No |
Images to attach to the response |
witness_statement.incident_id |
Integer | Yes |
The ID of the Incident |
witness_statement.witness_id |
Integer | Yes |
Witness ID |
witness_statement.drawing_revision_ids[] |
Array | No |
Drawing Revisions to attach to the response |
witness_statement.date_received |
String | No |
Date that the Witness Statement was received. This assumes the dates provided are in the project timezone. |
witness_statement.recording |
Object | No | |
witness_statement.recording.upload_id |
String | No |
Recording Upload ID |
witness_statement.custom_field_%{custom_field_definition_id} |
No |
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 of the Custom Field Definition's LOV Entries. For a lov_entries data_type the value passed in should be an array of IDs of the Custom Field Definition's LOV Entries. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.