PATCH /rest/v1.0/projects/{project_id}/incidents/environmentals/{id}

Updates the Environmental record

Servers

Path parameters

Name Type Required Description
id Integer Yes

Environmental ID

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.

Query parameters

Name Type Required Description
incident_id Integer No

Incident ID

Request body fields

Name Type Required Description
environmental Object Yes
environmental.description String No

Description of event in Rich Text format

environmental.quantity_unit_of_measure String No

Unit of measure for the "quantity" field

Possible values:

  • "ton"
  • "years"
  • "weeks"
  • "ls"
  • "hours"
  • "sy"
  • "months"
  • "m^3"
  • "t"
  • "mm"
  • "m^2"
  • "ea"
  • "kg"
  • "lbs"
  • "lf"
  • "m"
  • "days"
  • "cy"
  • "sf"
environmental.environmental_type_id Integer No

The ID of the Environmental Type

environmental.quantity_value Number No

Numeric portion of the "quantity" field

environmental.work_activity_id Integer No

The ID of the Work Activity

environmental.managed_equipment_id Integer No

The ID of the Managed Equipment

environmental.affected_company_id Integer No

The ID of the Affected Company

environmental.estimated_cost_impact Number No

Estimated cost impact of the record

environmental.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

  1. Add HTTP Task to your workflow definition.
  2. 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.
  3. Click Test request to test run your request to the API and see the API's response.