PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/{id}
JSON body may be either:
- Nested (recommended): a
coordination_issueobject with attributes to update, or - Flat: the same attribute keys at the root of the JSON (no
coordination_issuewrapper).
Updates use CoordinationIssues::Public::UpdateService. bim_file_id is mapped to the internal file association.
status: in_progress: Requires enable-ci-in-progress; otherwise coerced to open before persist.
is_private: Optional boolean; when sent, persisted on update (see update schema).
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
Coordination Issue ID (numeric) |
project_id |
String | Yes |
Unique identifier for the project. |
company_id |
String | Yes |
Unique identifier for the company. |
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. |
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.