Reject Repair
POST/api/repairs/:repair/reject
Declines a claim at triage (not covered, misuse, duplicate). The repair moves to rejected, any RMA created for it is canceled and unused inbound labels are voided.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Fields:
reason(string, required, 3–500 characters) — shown in the activity log and to the customer.notify_customer(boolean, optional, defaulttrue) — sends the "Not covered" email with the reason and, when the unit's warranty policy offers paid repairs, an offer to repair it for a fee. The email is skipped when the template is switched off in email templates or the customer has no email address; the response message says which happened. Sendfalseto reject silently.
Authentication: Bearer token with the repairs:write scope.
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.