Errors

Update an error issue status

PATCH/api/websites/{websiteId}/errors/{issueId}

Changes the status of an error issue to unresolved, resolved, or ignored. Changing the status does not discard new occurrences.

Try it

Headers

Name	Type	Description
Authorizationrequired	string	Token returned by POST /api/auth/login, or an API key (`umami_…`) created under Settings → API keys (self-hosted only). `Bearer <token>`.

Path parameters

Name	Type	Description
websiteIdrequired	string	ID of the website.
issueIdrequired	string	ID of the error issue.

Request body

Name	Type	Description
statusrequired	enum<string>	New status of the issue. Options: `unresolved`, `resolved`, `ignored`

Example request

{
  "status": "unresolved"
}

Responses

200Successful response.

Name	Type	Description
okrequired	boolean	Whether the operation succeeded.

200 example

{
  "ok": true
}

400Invalid request.

Name	Type	Description
errorrequired	object	Error details returned when the operation fails.

400 example

{
  "error": {
    "code": "string",
    "message": "string",
    "status": -9007199254740991
  }
}

401Authenticated website access required.

Name	Type	Description
errorrequired	object	Error details returned when the operation fails.

401 example

{
  "error": {
    "code": "string",
    "message": "string",
    "status": -9007199254740991
  }
}

404Website, issue, or occurrence not found.

Name	Type	Description
errorrequired	object	Error details returned when the operation fails.

404 example

{
  "error": {
    "code": "string",
    "message": "string",
    "status": -9007199254740991
  }
}

Code samples

cURL

curl -X PATCH 'https://api.example.com/api/websites/{websiteId}/errors/{issueId}' \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{
  "status": "unresolved"
}'

PreviousGet an error issue NextList error occurrences