GET /rest/v1.0/coordination_issues

Lists Coordination Issues associated with the specified Project.

Servers

https://api.procore.com

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
`filtersdue_date`	String	No	Filter item(s) within a specific due date iso8601 date range.
`project_id`	Integer	Yes	Unique identifier for the project.
`viewpoint_format`	String	No	Specify viewpoint data format. This parameter functions only when the query parameter view is 'extended' The default format returns the viewpoint content as saved. The procore format returns the viewpoint content converted to Procore format. If a valid conversion is not possible, empty viewpoint is returned. Possible values: `"procore"` `"default"`
`filterscreated_at`	String	No	Filter item(s) within a specific created at iso8601 datetime range.
`sort`	String	No	Sort item(s) by an attribute. The default sort is ascending. To sort in descending order, prepend the sort value with a hyphen character '-' Possible values: `"due_date"` `"company_then_status"` `"location_then_created_at"` `"location_then_issue_type"` `"location"` `"issue_number"` `"location_then_issue_number"` `"location_then_due_date"` `"issue_type"` `"location_then_priority"` `"trade"` `"priority"` `"location_then_trade"`
`filterspriority[]`	Array	No	Filter item(s) with matching priority.
`filterslocation_id[]`	Array	No	Filter item(s) with matching locations.
`filtersassignee_company_id[]`	Array	No	Filter item(s) with matching assignee vendor companies.
`view`	String	No	The compact view contains only ids. The normal view is a subset of the response shown below, and does not include attachments, viewpoints, linked items and updated_by The extended view contains the response shown below. The default view is normal. Possible values: `"extended"` `"normal"` `"compact"`
`filtersids[]`	Array	No	Filter item(s) with matching ids.
`page`	Integer	No	Page
`filterscoordination_issue_file_id[]`	Array	No	Filter item(s) with the exact coordination issue file.
`save_sticky_filters`	Boolean	No	Persists filter parameters for the requesting user and project.
`filtersissue_type[]`	Array	No	Filter item(s) with matching issue_type.
`per_page`	Integer	No	Elements per page
`filtersstatus[]`	Array	No	Filter item(s) with matching status.
`filtersassignee_id[]`	Array	No	Filter item(s) with matching assignees.
`filterssearch`	String	No	Filter item(s) with the matching search query. The search is performed on title and issue number.
`filtersupdated_at`	String	No	Filter item(s) within a specific updated at iso8601 datetime range.
`filterscreated_by_id[]`	Array	No	Filter item(s) with matching User IDs.
`filterscreated_from[]`	Array	No	Filter item(s) with matching creation source.
`filtersinclude_sublocations`	Boolean	No	Use together with `filters[location_id]` Default value: false
`filterstrade_id[]`	Array	No	Filter item(s) with matching trades.

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.