Create A Model Manager Viewpoint And Link It To The Issue (REST V2.0)
create_a_model_manager_viewpoint_and_link_it_to_the_issue_restCreate a Model Manager viewpoint and link it to a coordination issue in Procore. Requires company, project, coordination issue, scene, and BIM model UUID.
Instructions
Proxies to Model Manager POST /rest/v2.0/companies/{company_id}/projects/{project_id}/bim/viewpoints (RequestsCreateViewpointRequest: scene_id, optional name, payload per MM OpenAPI), plus Procore-required bim_model_uuid for application validation. Then inserts coordination_issue_bim_viewpoints with viewpoint_uuid (MM viewpoint id). Optional observer/notification side effects enqueue CoordinationIssues::ObserverWorker. Use this to create a new Coordination Issues in Procore. Creates a new Coordination Issues and returns the created object on success (HTTP 201). Required parameters: company_id, project_id, coordination_issue_id, scene_id, bim_model_uuid. Procore API (v2.0): Project Management > Coordination Issues. Endpoint: POST /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 | |
| name | No | JSON request body field — optional viewpoint name (MM `RequestsCreateViewpointRequest.name`). | |
| scene_id | Yes | JSON request body field — scene UUID (MM `scene_id` / `UuidUUID`). | |
| bim_model_uuid | Yes | JSON request body field — required by Procore `ViewpointCreateViaModelManagerService` validation (not sent to MM create as a top-level field). | |
| payload | No | JSON request body field — the payload for this Coordination Issues operation | |
| camera_data | No | JSON request body field — used when top-level `payload` is absent — becomes `camera` in the MM payload. Send a JSON object or a JSON string (parsed server-side). | |
| redlines_data | No | JSON request body field — used when top-level `payload` is absent — becomes `markup` in the MM payload (object or JSON string). | |
| sections_data | No | JSON request body field — used when top-level `payload` is absent — parsed value is set on `clipping.planes` in the MM payload. Model Manager expects an array of clipping planes (`TypesClippingPlane`); object or JSON string... | |
| render_mode | No | JSON request body field — the render mode for this Coordination Issues operation | |
| bim_file_id | No | JSON request body field — accepted in the JSON body for parity with other viewpoint APIs; **not** applied by MM create in this flow. | |
| bim_view_folder_id | No | JSON request body field — accepted in the JSON body for parity with other viewpoint APIs; **not** applied by MM create in this flow. | |
| snapshot_upload_uuid | No | JSON request body field — accepted in the JSON body; **not** applied by MM create in this flow unless part of `payload`. | |
| primary | No | JSON request body field — sets `is_primary` on the coordination-issue viewpoint mapping. | |
| position | No | JSON request body field — sets ordering `position` on the coordination-issue viewpoint mapping (auto-incremented if omitted). | |
| visibility | No | JSON request body field — the visibility for this Coordination Issues operation |