POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/projects/{project_id}

Updats a single project given a company ID and project ID and body params

Servers

Path parameters

Name Type Required Description
project_id Integer Yes

Unique identifier for the project

company_id Yes

Unique identifier for the company. This parameter accepts both formats:

  • Recommended: Procore company ID (integer) - Use this for new integrations
  • Legacy: LaborChart UUID format (uuid string) - Supported for backward compatibility

A proxy layer automatically handles both formats, but using the Procore company ID is preferred for consistency with other Procore APIs.

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
timezone String No

The timezone to use for scheduling outbound messages for the Project. If not provided, the Group timezone will be used.

name String Yes

The name of the Project.

start_date String No

Project's start date. Required if status is active.

daily_start_time String No

Default time the Project's workday begins. Must follow HH:MM am/pm format. Allowed increments: 15 minutes.

daily_end_time String No

Default time the Project's workday ends. Must follow HH:MM am/pm format. Allowed increments: 15 minutes.

status String Yes

Controls Project visibility and filtering. active - Project is currently in progress. pending - Project is planned but not started. inactive - Project is no longer active.

Possible values:

  • "inactive"
  • "active"
  • "pending"
job_title_id String No

UUID of the Job Title for the Role. If omitted, the Person's default Job Title is used.

color String No

Hexadecimal color code for the Project. Helps with categorization and visual distinction.

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.