Send an alert to the DevOps employee
For your monitoring, with an API key. The DevOps employee prepares a triage summary for a person to approve.
POST
/
employees
/
devops
/
alerts
Send an alert to the DevOps employee
curl --request POST \
--url https://app.mithunai.com/mithunai/api/v1/employees/devops/alerts \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"service": "<string>",
"title": "<string>"
}
'import requests
url = "https://app.mithunai.com/mithunai/api/v1/employees/devops/alerts"
payload = {
"service": "<string>",
"title": "<string>"
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({service: '<string>', title: '<string>'})
};
fetch('https://app.mithunai.com/mithunai/api/v1/employees/devops/alerts', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"results": [
{}
],
"ignored": {}
}Use an API key whose role is Owner, Admin or Editor: it needs
agent.update, and an Editor key is
the least it takes. Any other role is refused with 403.
The employee only ever proposes: a person decides, and a remediation is never run. The same service
and title again within the hour files nothing more. Past your organisation’s limit for the day
nothing is filed and the answer says so.
AI employees are in beta. Every route answers
404 unless your deployment has switched the
beta on, and these routes need a second switch, off by default. See Work that arrives by
itself. No real Grafana has sent one of these yet.Body
string
required
The service it is about. Letters, digits, dots, dashes and underscores.
string
required
What the alert is.
string
A short word, such as
critical or warning.From Grafana
Or send a Grafana alert webhook’s own body: point a webhook contact point at this address and put the key in its authorization header credentials. From each alert inalerts, this reads status, the
labels alertname, severity and the first of service, service_name, app, job, and the
annotation summary. Nothing else in it is read, and no URL in it is followed. A resolved alert files
nothing. At most 10 alerts are filed per request.
Response
object[]
required
One per alert:
service, title, status and task_id. status is filed, repeat
(task_id is the work already filed) or over_limit.object
required
How many were not filed:
resolved, no_service and over_request_limit.Last modified on November 4, 2026
Send an alert to the DevOps employee
curl --request POST \
--url https://app.mithunai.com/mithunai/api/v1/employees/devops/alerts \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"service": "<string>",
"title": "<string>"
}
'import requests
url = "https://app.mithunai.com/mithunai/api/v1/employees/devops/alerts"
payload = {
"service": "<string>",
"title": "<string>"
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({service: '<string>', title: '<string>'})
};
fetch('https://app.mithunai.com/mithunai/api/v1/employees/devops/alerts', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"results": [
{}
],
"ignored": {}
}