File Reimbursement Case
POST/api/amazon/unified/reimbursement-cases/:reimbursementCase/file
Records the case ID Amazon gave you after you opened the claim in Seller Central, and moves the case to submitted (Waiting on Amazon). A note is added to the case.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Request body fields:
amazon_case_id(required, string) — the Amazon case ID. Anything pasted is normalised to its digits first (e.g.Case ID: 1645 123 4567becomes16451234567); the result must be 8 to 15 digits.
Optimistic locking: if someone else already filed the case, the response is 409 Conflict with who filed it and the Amazon case ID on file. Re-sending the same case ID as the person who filed it is a no-op that returns the case. A case that can no longer be filed (paid, dismissed, expired…) returns 422, and so does an informational case (informational: true), which is a heads-up with nothing to file.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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.
Conflict
Response Headers
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.