File Reimbursement Case Revaluation
POST/api/amazon/unified/reimbursement-cases/:reimbursementCase/revaluation
Records the case Amazon's Reimbursement Revaluation Tool opened when Amazon paid a claim below the unit's value. Amazon only raises a reimbursement through that tool (a reply on the original case asking for the rest is refused), and the tool always opens a new case.
recovery:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The new case becomes the current amazon_case_id; the earlier ones stay in amazon_cases, and a payment Amazon makes on any of them is matched to this opportunity. A partially_reimbursed or reimbursed case moves back to submitted (Waiting on Amazon). A note is added.
Request body fields:
amazon_case_id(required, string) — the case ID the tool gave you. Normalised to its digits; must be 8 to 15 digits.
Returns 422 when Amazon has not paid anything on the case, the case is closed, the ID is already recorded on it, or the ID is one of the case's reimbursement IDs.
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 Content
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.