GET /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/{coordination_issue_id}/viewpoints

GET collection — returns every viewpoint mapping on the issue. Legacy rows (join has bim_viewpoint_id) use BimViewpointBlueprint view :procore_v0_1 — the same shape as the viewpoints array on the coordination issue resource (CoordinationIssueBlueprint view :extended_with_viewpoint_v0_1): camera_data, sections_data, redlines_data, snapshot, bim_file_id, uuid, numeric id, etc.

MM-backed rows (viewpoint_uuid only) are loaded in bulk from Model Manager (POST .../bim/viewpoints/batch) and appear as full MM viewpoint objects (same shape as GET .../viewpoints/{uuid} inner data).

Order follows the join table: position, then created_at. Pagination counts join rows, not only legacy viewpoints.

Supports pagination (page, per_page; default per page 10, max 100 per Rest::V2::ApplicationController / RestV2Pagination).

Response headers may include Per-Page, Total, and Link (RFC 5988) for pagination.

502 if Model Manager returns 5xx while resolving MM-backed rows on this page.

Servers

https://api.procore.com

Path parameters

Name	Type	Required	Description
`project_id`	String	Yes	Unique identifier for the project.
`coordination_issue_id`	String	Yes	Coordination Issue ID
`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
`page`	Integer	No	Page
`included`	String	No	Ignored. Legacy list items always return the full `:procore_v0_1` blueprint shape; MM-backed rows always return the full Model Manager viewpoint object.
`per_page`	Integer	No	Elements per page Default value: 10
`primary`	Boolean	No	When `true`, only mappings marked primary on the issue are returned. When `false`, only non-primary mappings. When omitted, all mappings are returned (subject to pagination). Applies to both the full list and `view=ids_only`.
`view`	String	No	When `ids_only`, response body is `{ "data": [...] }`: legacy mappings use integer `bim_viewpoint_id`; MM-backed mappings use UUID strings. Order matches the full list (`position`, `created_at`). Valid values: `"ids_only"`

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.