Create Incident
create_incidentCreate a project incident with title and event date, attach related records like injuries or property damages, and enforce custom validation rules. Idempotent via UUID deduplication.
Instructions
Creates a new incident in the specified project. Requires at minimum a title and event_date. Optionally attach associated records (injuries, near_misses, environmentals, property_damages) in a single request. Pass run_configurable_validations=true to enforce any custom validation rules configured for the Incidents tool. The operation is idempotent via UUID-based deduplication. Pass the record's fields as top-level arguments — they are nested under "incident" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted. Acts on the incident and returns Procore's response for the operation. 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. Procore API: Project Management > Incidents. Endpoint: POST /rest/v1.0/projects/{project_id}/incidents
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | JSON request body field — incident Title | |
| status | No | JSON request body field — status (Not updatable if an incident has a workflows instance) | |
| private | No | JSON request body field — indicates whether an Incident is private | |
| 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. | |
| form_ids | No | JSON request body field — forms to attach to the response | |
| injuries | No | JSON request body field — associated Injuries to create | |
| hazard_id | No | JSON request body field — unique identifier of the hazard | |
| image_ids | No | JSON request body field — images to attach to the response | |
| 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. | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| recordable | No | JSON request body field — indicates whether an Incident is recordable | |
| description | No | JSON request body field — description of the Incident | |
| location_id | No | JSON request body field — the ID of a Location | |
| near_misses | No | JSON request body field — associated Near Misses to create | |
| 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. | |
| time_unknown | No | JSON request body field — indicates that the time of the Incident occurrence is unknown | |
| upload_uuids | No | JSON request body field — array of uploaded file UUIDs. | |
| environmentals | No | JSON request body field — associated Environmentals to create | |
| 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. | |
| file_version_ids | No | JSON request body field — file Versions to attach to the response | |
| property_damages | No | JSON request body field — associated Property Damages to create | |
| drawing_revision_ids | No | JSON request body field — drawing Revisions to attach to the response | |
| 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) | |
| 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 | |
| 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... | |
| witness_statements_attributes | No | JSON request body field — associated Witness Statement to create | |
| 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 ... |