Update bug report status

PATCHhttps://app.speybooks.com/api/v1/admin/bug-reports/{id}

Update the status and the admin notes of a bug report. Severity is set when the report is created and is not changed through this surface.

Request body: status (optional, one of open, acknowledged, investigating, resolved, wont_fix, duplicate) and adminNotes (optional, up to 5000 characters).

Moving to a terminal status (resolved, wont_fix, duplicate) records the resolution time and emails the reporter with the bug title, the public id, and the human-readable status. Moving a terminal report back to a non-terminal status clears the recorded resolution time. The email is sent only on terminal transitions; a send failure is recorded but does not fail the request.

Note: admin notes are shown to the reporter in their own view of the report. Treat them as reporter-facing, not as an internal-only channel.

Returns 404 if the public id matches no report, and a no-change result if no fields are supplied.

Path parameters

idstringrequired

Response

200Bug report updated. Email sent to reporter if status changed to a closed state.

Show response fields

idstring

messagestring

Error codes

404Bug report not found.

RequestPATCH/v1/admin/bug-reports/{id}curl

curl -X PATCH https://api.speybooks.com/v1/admin/bug-reports/bug_7k3m \
  -H "Authorization: Bearer <admin-token>" \
  -H "Content-Type: application/json" \
  -d '{"status": "resolved", "adminNotes": "Fixed; the VAT number now renders from the organisation settings."}'

Response200

{
  "success": true,
  "data": {
    "message": "Bug report updated",
    "id": "bug_7k3m"
  }
}