---
title: "Open Alert Investigation"
method: POST
path: "/api/alerts/{alert_id}/investigation"
tags: ["monitoring"]
---

# Open Alert Investigation

`POST /api/alerts/{alert_id}/investigation`

## Request

- Base URL: `https://app.myriade.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://app.myriade.ai/api/alerts/{alert_id}/investigation`
- Auth: none declared

Get-or-create the alert's investigation conversation (3c).

The mail/inbox deep link lands here: a focused follow-up thread for THIS
alert (and the sibling checks its details reference via ``<CHECK:id>``),
distinct from the mixed-topic review conversation. Idempotent — re-opening
the same alert returns the same conversation, so a refresh or a second click
on the email never spawns a new thread.

Gated on read access (like ``get_alert``) — except on governed databases,
where it is manager-only: the conversation-load grant
(``user_can_use_alert_conversation``) restricts governed threads to
managers, so letting a non-manager create/own the alert's single shared
thread would strand every later reader (and seed the thread with
redacted context). Matches the review-conversation rule.

## Path parameters

- `alert_id` string, uuid, required

## Cookies

- `session` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/myriade/apis/myriade-bi-api.md) · [All operations](https://skmtc.dev/myriade/apis/myriade-bi-api/llms.txt) · [OpenAPI document](https://skmtc.dev/myriade/apis/myriade-bi-api/revisions/15b7cb96ca80?raw)