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

Creates an issue via CoordinationIssues::Public::CreateService. Request body is flat JSON (not wrapped in coordination_issue). See create schema for which fields are persisted vs accepted-only.

status: in_progress: Requires enable-ci-in-progress; otherwise coerced to open before persist.

is_private: Optional boolean; when sent, persisted on create (see create request schema).

Observers may enqueue notifications / activity side effects.

Servers

https://api.procore.com

Path parameters

Name	Type	Required	Description
`project_id`	String	Yes	Unique identifier for the project.
`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
`project_id`	String	No	Path includes project; may be echoed in body (ignored for scoping).
`description`	String	No	Permitted by controller; not applied by `CreateService` — use PATCH to set.
`watcher_ids[]`	Array	No	User ids to add as watchers on the new coordination issue.
`status`	String	No	Initial status (e.g. `open`, `closed`, `in_progress`). `in_progress` is accepted only when `enable-ci-in-progress` is active for the project/company; otherwise the API coerces it to `open` before create. Subject to model validations. Response `status` follows `CoordinationIssue#status` (may show `open` when the feature is off even if related persistence rules apply).
`company_id`	String	No	Company id for the new issue (typically matches path company).
`bim_model_id`	String	No
`is_private`	Boolean	No	When `true`, creates a private coordination issue (restricted visibility). Omitted keys leave the column at its default (typically public).
`trade_id`	String	No
`location_id`	String	No	Location id scoped to the project.
`priority`	String	No	Permitted by controller; not applied by `CreateService` — use PATCH to set.
`bim_file_id`	String	No	BIM file id for the coordination issue file association.
`assignee_id`	String	No	Login information / user id for assignee.
`attachment_upload_uuids[]`	Array	No	Prostore upload UUIDs for new attachments.
`title`	String	Yes	Required issue title.
`origin`	Object	No	Optional origin metadata stored with the issue when created or updated.
`origin.origin_type`	String	No
`origin.origin_id`	String	No
`origin.title`	String	No
`origin.deep_link_url`	String	No
`creation_source`	String	No
`issue_type`	String	No	Permitted by controller; not applied by `CreateService` — use PATCH to set.
`due_date`	String	No	Permitted by controller; not applied by `CreateService` — use PATCH to set.

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.