Generate Reimbursement Case Text
POST/api/amazon/unified/reimbursement-cases/:reimbursementCase/case-text
Regenerates the case text synchronously (usually well under 30 seconds). AI is used when it is configured for the account; otherwise a template is used, so this always returns text. An explicit regenerate replaces text a user edited.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Request body fields:
tone(optional, string) —concise(default) ordetailed.purpose(optional, string) —claim(default),reply(reply to a partial payment) orappeal(appeal a denial).
The response's claim_text_source is ai or template and claim_text_purpose echoes the purpose.
Returns 409 Conflict when the case changed while the text was being written (new facts, a user edit, a filing). The generated text is not saved; the response carries a message and the case as it is now in data. Review the case and try again.
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.