Skip to main content

Update Issue Type

PUT 

/api/repairs/issue-types/:type

Updates an issue type. Send only the fields to change. Moving a type (changing parent_id) is refused when the tree would become more than 3 levels deep. Requires the Repairs: Settings permission.

Required scope: repairs:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Fields:

  • name (string, optional, max 80) — the name technicians see.
  • parent_id (integer, optional, nullable) — the issue type to nest this under. Types go at most 3 levels deep. A type can't be its own parent.
  • customer_label (string, optional, nullable, max 80) — the wording shown to customers on the claim form and status page; falls back to name.
  • default_root_cause (string, optional, nullable) — the root cause pre-filled when a technician picks this issue: manufacturing_defect, wear_and_tear, accidental_damage, misuse, shipping_damage, no_fault_found, unknown.
  • standard_minutes (integer, optional, nullable, 0–65535) — the standard labour time for this fix.
  • bill_flat_price (number, optional, nullable, 0–99999999) — a flat price to charge for this fix on out-of-warranty quotes.
  • portal_visible (boolean, optional) — whether customers can pick this issue on the claim form.
  • sort_order (integer, optional, min 0) — position among its siblings; new types go last when omitted.

Authentication: Bearer token with the repairs:write scope.

Request​

Responses​

OK

Response Headers
    Content-Type