PATCH /rest/v1.0/projects/{project_id}/schedule

Updates the Schedule integration type for a project.

Schedule Types

TypeKey
File-based schedule integration via web browser"Microsoft Project"
File-based schedule integration via Procore Drive"Microsoft Project 2010"
File-based schedule integration via Procore Documents"Microsoft Project Documents"
Primavera P6 database integration via Procore Drive"Primavera P6"

Note that the schedule types listed as "Microsoft Project", "Microsoft Project 2010", and "Microsoft Project Documents" are functionally identical. In all cases Procore can consume any supported schedule file type and extract data from it, not just Microsoft Project. Schedule files can be uploaded either via Procore Drive, via the Procore Documents tool, or via the Procore Schedule tool, regardless of which of these three types is selected. Where Primavera P6 database integration via Procore Drive is in use, the p6_id attribute returned by this API indicates which P6 project Procore Drive is extracting data from.

Servers

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

The ID of the Project the Schedule Type belongs to

type Object Yes

Schedule Type object

type.key String No

The Key of the Schedule Type

Possible values:

  • "Primavera P6"
  • "Microsoft Project Documents"
  • "Microsoft Project 2010"
  • "Microsoft Project"
type.p6_id String No

The Primavera P6 Identifier of the Schedule Type

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.