Save Line Diagnosis
PUT/api/repairs/:repair/lines/:line/diagnosis
Records the technician's diagnosis on one unit. Send only the fields to change. When the root cause or the issue lists change, warranty coverage is re-evaluated; if coverage changes, unposted costs on the unit move to the new default bill-to, and the response says how many posted costs need reclassing. The message names the coverage change when one happened. Requires the Repairs: Bench & timers permission.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Fields:
found_issue_type_ids(array of integers, optional, max 50, distinct) — issues the technician found; replaces the current list.reported_issue_type_ids(array of integers, optional, max 50, distinct) — issues the customer reported; replaces the current list.root_cause(string, optional, nullable) — manufacturing_defect, wear_and_tear, accidental_damage, misuse, shipping_damage, no_fault_found, unknown.fault_attribution(string, optional, nullable) — who caused the fault: supplier, brand_process, carrier, customer, none.notes(string, optional, nullable, max 10000) — diagnosis notes.component_product_id(integer, optional, nullable) — for a set or bundle, the piece of the set that is faulty. Must be a component of the unit's product.
Response fields:
coverage,coverage_label,coverage_reasons— the unit's coverage after the save (in_warranty, out_of_warranty, goodwill, unknown).coverage_changed,previous_coverage— whether and from what coverage changed.next_step—quote_or_declinewhen the unit just became out of warranty, else null.unposted_costs_updated— costs moved to the new default bill-to.posted_costs_to_reclass— already-posted costs that still carry the old bill-to.default_bill_to— warranty, goodwill or customer.risk_signals— the unit's current risk signals.
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
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.