List Coordination Issue Viewpoints (Legacy + Model Manager, REST V2.0)
list_coordination_issue_viewpoints_legacy_model_manager_rest_v2List viewpoint mappings for a coordination issue, including legacy BIM viewpoints and model-manager viewpoints. Supports pagination and filtering by primary status.
Instructions
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 M... Use this to enumerate Coordination Issues when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Coordination Issues. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, project_id, coordination_issue_id. Procore API (v2.0): Project Management > Coordination Issues. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/coordination_issues/{coordination_issue_id}/viewpoints
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company_id | Yes | URL path parameter — unique identifier for the company. | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| coordination_issue_id | Yes | URL path parameter — coordination Issue ID | |
| view | No | Query string parameter — 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`). | |
| page | No | Query string parameter — page number for paginated results (default: 1) | |
| per_page | No | Query string parameter — number of items per page (default: 100, max: 100) | |
| primary | No | Query string parameter — 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 fu... | |
| included | No | Query string parameter — **Ignored.** Legacy list items always return the full `:procore_v0_1` blueprint shape; MM-backed rows always return the full Model Manager viewpoint object. |