Transition Reimbursement Case Status
POST/api/amazon/unified/reimbursement-cases/:reimbursementCase/transition
Moves a reimbursement case to a new lifecycle status, enforcing the allowed transitions and recording a case note describing the change.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Request body fields:
status(required) — target status, one of: potential, under_review, ready_to_submit, submitted, partially_reimbursed, reimbursed, denied, dismissed, expired.reason(optional, string, max 255) — stored as the dismissal/denial reason when moving todismissedordenied, and appended to the transition note.amazon_case_id(optional, string, max 64) — when provided together withstatus=submitted, the case is marked as submitted to Amazon with this Seller Central case ID andsubmitted_atis stamped (the case must currently be in potential, under_review or ready_to_submit).
Allowed transitions:
- potential -> under_review, ready_to_submit, submitted, dismissed, expired
- under_review -> potential, ready_to_submit, submitted, dismissed, expired
- ready_to_submit -> under_review, submitted, dismissed, expired
- submitted -> partially_reimbursed, reimbursed, denied
- partially_reimbursed -> reimbursed, denied
- reimbursed, denied, dismissed and expired are terminal (no outgoing transitions). Transitioning to the current status is a no-op.
An invalid transition returns HTTP 422 with an error message.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.