Send Repair Email
POST/api/repairs/:repair/communications
Send Repair Email.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Request fields:
template_type(required): string, In:in:"repair_update","repair_info_requested","repair_delay","repair_shipping_instructions","repair_completed_shipped","repair_quotemessage(optional): string, max:5000to_email(optional): email:filter, max:190
Permission: repairs.update.
Authentication: Bearer token with the repairs:read / 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 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.