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

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.

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
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`Procore-Company-Id`	Integer	Yes	Unique company identifier associated with the Procore User Account.

Request body fields

Name	Type	Required	Description
`bim_model_uuid`	String	Yes	Required by Procore `ViewpointCreateViaModelManagerService` validation (not sent to MM create as a top-level field).
`sections_data`		No	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 is accepted and passed through after parse.
`scene_id`	String	Yes	Scene UUID (MM `scene_id` / `UuidUUID`).
`snapshot_upload_uuid`	String	No	Accepted in the JSON body; not applied by MM create in this flow unless part of `payload`.
`primary`	Boolean	No	Sets `is_primary` on the coordination-issue viewpoint mapping.
`camera_data`		No	Used when top-level `payload` is absent — becomes `camera` in the MM payload. Send a JSON object or a JSON string (parsed server-side).
`position`	Integer	No	Sets ordering `position` on the coordination-issue viewpoint mapping (auto-incremented if omitted).
`visibility`	Object	No
`bim_file_id`	String	No	Accepted in the JSON body for parity with other viewpoint APIs; not applied by MM create in this flow.
`name`	String	No	Optional viewpoint name (MM `RequestsCreateViewpointRequest.name`).
`payload`		No
`render_mode`	String	No	Default value: "shaded"
`bim_view_folder_id`	String	No	Accepted in the JSON body for parity with other viewpoint APIs; not applied by MM create in this flow.
`redlines_data`		No	Used when top-level `payload` is absent — becomes `markup` in the MM payload (object or JSON string).

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.