GET /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/workflow_issues
Returns a list of Coordination Issues that have associated workflow metadata. Issues are filtered based on user visibility rules:
- Project Admins can see all workflow issues
- Issue creators can see issues they created
- Issue assignees can see issues assigned to them
- Workflow members can see issues for workflows they are part of
Include
permissionsin the query to getcan_editfield for each issue.
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
project_id |
String | Yes |
Unique identifier for the project. |
company_id |
String | Yes |
Unique identifier for the company. |
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 |
|---|---|---|---|
viewpoint_format |
String | No |
Specifies the format for viewpoint data. Use 'procore' for Procore format, 'bcf' for BCF format. Valid values:
Default value: "procore" |
filters[created_at] |
String | No |
Return item(s) created within the specified ISO 8601 datetime range.
Formats:
|
filters[priority][] |
Array | No |
Filter item(s) by priority level. |
included |
String | No |
Comma-separated list of fields to include in the response. |
filters[id][] |
Array | No |
Filter by specific Coordination Issue IDs. |
filters[search] |
String | No |
Returns item(s) matching the specified search query string. |
filters[document_revision_id][] |
Array | No |
Filter Coordination Issues by document revision ID(s). |
filters[updated_at] |
String | No |
Return item(s) last updated within the specified ISO 8601 datetime range.
Formats:
|
filters[include_sublocations] |
Boolean | No |
Use together with Default value: false |
filters[trade_id] |
String | No |
Trade ID |
filters[issue_type][] |
Array | No |
Filter item(s) by issue type. |
filters[due_date] |
String | No |
Filter Coordination Issues by due date. |
sort |
String | No |
Sort results by field. Direction (asc/desc) controlled by presence or absence of '-' prefix. Valid values:
|
filters[assignee_id][] |
Array | No |
Filter item(s) with matching assignee user IDs. |
filters[created_by_company_id][] |
Array | No |
Filter item(s) with matching created by vendor companies. |
filters[document_container_id][] |
Array | No |
Filter Coordination Issues by document container ID(s). |
filters[created_from][] |
Array | No |
Filter item(s) by creation source. |
filters[status] |
String | No |
Return item(s) with the specified statuses |
view |
String | No |
Specifies the view to use for the response. Use 'normal' for basic fields, 'extended' for full details including viewpoints and attachments. Valid values:
Default value: "normal" |
filters[location_id] |
String | No |
Filters by specific location (Note: Use either this or location_id_with_sublocations, but not both) |
filters[overdue] |
Boolean | No |
Filter for overdue Coordination Issues. |
page |
Integer | No |
Page |
per_page |
Integer | No |
Elements per page Default value: 10 |
filters[created_by_id][] |
Array | No |
Return item(s) created by the specified User IDs |
filters[assignee_company_id][] |
Array | No |
Filter item(s) with matching assignee vendor companies. |
filters[source_file_id][] |
Array | No |
Filter by source BIM file ID |
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.