Update a support request status

Status transitions with the same semantics as the admin inbox: closed closes with a resolution (default resolved) + optional note; a closed request can only transition to open (reopen, which clears the resolution); other transitions update the status (optional subStatus). Scope: support:write.

PATCHhttps://api.helpbento.com/v1/support-requests/{id}

Authentication

AuthorizationstringheaderBearer <token>required

An API key, e.g. hb_live_… (live) or hb_test_… (test).

Path parameters

1 param

idstringrequired

Header parameters

1 param

Idempotency-Keystringlength: 0…255
Optional idempotency key (1–255 chars). Repeating a mutating request with the same key within 24h replays the original response instead of re-executing it; a concurrent in-flight request with the same key returns 409. Use a unique key (e.g. a UUID) per logical operation so network retries are safe.

Request body

application/jsonrequired

statusstringpending | investigating | open | closedrequired
subStatusstring | nullawaiting_reply
resolutionstringresolved | unresolved
Only with status=closed (default resolved).
resolutionNotestring
Only with status=closed.

Responses

idstring
statusstringpending | investigating | open | closed

Errors

curl -X PATCH "https://api.helpbento.com/v1/support-requests/<id>" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "status": "pending",
  "subStatus": "awaiting_reply",
  "resolution": "resolved",
  "resolutionNote": "string"
}'

{
  "id": "string",
  "status": "pending"
}