PATCH /rest/v1.0/tasks/sync

This endpoint creates or updates a batch of tasks.

Servers

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
project_id Integer Yes

Unique identifier for the project.

Request body fields

Name Type Required Description
project_id Integer Yes

The ID of the Project the Tasks belongs to

updates[] Array Yes
updates[].finish String No

Task finish timestamp.

updates[].milestone Boolean No

True if this task is a milestone.

updates[].percentage Integer No

Percent complete value for this task.

updates[].critical_path Boolean No

True if this task is on the critical path.

updates[].baseline_start String No

The baseline start timestamp for this task.

updates[].parent_id Integer No

ID of the parent task.

updates[].source_uid String No

The unique identifier for this task from the external system which owns the schedule data.

updates[].resource_ids[] Array No

Resources assigned to this task, represented as an array of resource ID values.

updates[].actual_finish String No

Actual finish timestamp for this task.

updates[].schedule_duration Number No

The duration of this task in days as defined by the external system which owns the schedule data.

updates[].actual_start String No

Actual start timestamp for this task.

updates[].baseline_finish String No

The baseline finish timestamp for this task.

updates[].name String No

Task name.

updates[].activity_id String No

For tasks imported from external systems which have the concept of an "Activity ID" (for example Primavera P6), this attribute is used to hold the Activity ID value. Note that due to an oversight during the creation of this API, the value supplied here will be rendered as the schedule_activity_id attribute in the response body. This will be corrected in a later version of the API.

updates[].notes String No

Arbitrary notes about this task.

updates[].manually_edited Boolean No

Set to true if the task has been created or modified in Procore, false if the task was imported from an external schedule and has not been modified in Procore.

updates[].row_number Integer No

The row number of a task defines the sequence in which tasks are normally expected to be displayed.

updates[].finish_variance Number No

The finish variance in days for this task, as calculated by the external system which owns the schedule data.

updates[].has_children Boolean No

Flag set to true if this is a summary task, i.e. this task has child tasks.

updates[].full_outline_path String No

Task full outline path.

updates[].start_variance Number No

The start variance in days for this task, as calculated by the external system which owns the schedule data.

updates[].wbs String No

Work Breakdown Structure (WBS) number for this task.

updates[].start String No

Task start timestamp.

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.