Skip to main content

Transition Reimbursement Case Status

POST 
/api/amazon/unified/reimbursement-cases/:reimbursementCase/transition

Moves a case to another status. Allowed moves come from Get Reimbursement Case Transitions (e.g. denied → submitted to appeal).

Required scope: recovery:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Request body fields:

  • status (required, string) — one of: potential, under_review, ready_to_submit, submitted, partially_reimbursed, reimbursed, auto_reimbursed, denied, dismissed, expired.
  • reason (optional, string, max 255) — stored as the dismissal/denial reason and in the note.
  • amazon_case_id (optional, string) — when moving to submitted (including an appeal filed as a new Amazon case). Normalised to its digits; must be 8 to 15 digits.

A first filing — moving a case that has not been filed yet to submitted — works like File Reimbursement Case: if someone else already filed the case, the response is 409 Conflict with a message, who filed it (filed_by) and the Amazon case ID on file (amazon_case_id). Re-sending as the person who filed it (with no case ID or the same one) is a no-op that returns the case. Re-submitting a denied (appeal) or partially reimbursed (reply) case is a normal transition.

Returns 422 for a move that isn't allowed, including moving an informational case (informational: true) to submitted or ready_to_submit — informational cases are a heads-up with nothing to file. The case's allowed_transitions lists the moves it can make.

Moving a case to under_review puts it on hold (UI group on_hold): checked, but not claimable yet. A reason is required (422 without one) and is returned as dismissed_reason while the hold lasts; leaving under_review for any status other than dismissed/denied clears it.

Request​

Responses​

OK

Response Headers
    Content-Type