Update A Coordination Issue (REST V2.0)
update_a_coordination_issue_rest_v2_0Modify specific attributes of a coordination issue in Procore. Provide company, project, and issue ID; only supplied fields like title, assignee, or due date are updated.
Instructions
JSON body must include a coordination_issue object with attributes to update (CoordinationIssues::Public::UpdateService). bim_file_id is mapped to the internal file association. Use this to update an existing Coordination Issues (only the supplied fields are changed). Updates the specified Coordination Issues and returns the modified object on success. Required parameters: company_id, project_id, id. Procore API (v2.0): Project Management > Coordination Issues. Endpoint: PATCH /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/{id}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company_id | No | JSON request body field — unique identifier for the Procore company | |
| project_id | No | JSON request body field — unique identifier for the Procore project | |
| id | Yes | URL path parameter — coordination Issue ID (numeric) | |
| title | No | JSON request body field — the title for this Coordination Issues operation | |
| description | No | JSON request body field — the description for this Coordination Issues operation | |
| creation_source | No | JSON request body field — the creation source for this Coordination Issues operation | |
| location_id | No | JSON request body field — unique identifier of the location | |
| assignee_id | No | JSON request body field — unique identifier of the assignee | |
| bim_file_id | No | JSON request body field — unique identifier of the bim file | |
| bim_model_id | No | JSON request body field — unique identifier of the bim model | |
| due_date | No | JSON request body field — due date in YYYY-MM-DD format | |
| issue_type | No | JSON request body field — the issue type for this Coordination Issues operation | |
| priority | No | JSON request body field — the priority for this Coordination Issues operation | |
| trade_id | No | JSON request body field — unique identifier of the trade | |
| attachment_upload_uuids | No | JSON request body field — additional uploads to attach (same pipeline as create). | |
| origin | No | JSON request body field — optional origin metadata stored with the issue when created or updated. |