GET /rest/v1.0/projects/{project_id}/commitment_change_orders
Returns all Commitment Change Orders for the specified Project. This endpoint currently only supports projects using 1 and 2 tier change order configurations.
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
project_id |
Integer | Yes |
Unique identifier for the project. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Procore-Company-Id |
Integer | Yes |
Unique company identifier associated with the Procore User Account. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
filtersvendor_id |
Integer | No |
Filter results by Contract Vendor ID |
filtersexecuted |
Boolean | No |
Filter results by executed |
filterscontract_id |
Integer | No |
Filter results by Contract ID |
sort |
String | No |
Direction (asc/desc) can be controlled by the presence or absence of '-' before the sort parameter. Possible values:
|
filtersstatus |
String | No |
Filter results by status Possible values:
|
filtersupdated_at |
String | No |
Return item(s) within a specific updated at iso8601 datetime range |
filtersid |
Integer | No |
Filter results by Change Order ID |
filtersbatch_id |
Integer | No |
Filter results by Change Order Batch ID |
view |
String | No |
Specifies Which view (which attributes) of the resource is going to be present in the response. the extended view includes change events data, while the default view does not. Possible values:
|
filterslegacy_package_id |
Integer | No |
Filter results by legacy Change Order Package ID |
filterssignature_required |
Boolean | No |
Filter results by signature_required |
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.