Livo icon

Livo

Interact with Livo API for orders, products, customers, and repairs
Join our community

Actions21

Overview

The "Update Repair" operation in this node allows users to update an existing repair ticket in a repair management system via the Livo API. This operation is useful for scenarios where details of a repair need to be modified after creation, such as changing device information, updating accessories involved, or adjusting repair services and their pricing.

Practical examples include:

  • Correcting or adding device serial numbers or lock screen credentials.
  • Updating the list of accessories or device states related to the repair.
  • Modifying the repair services provided, including custom services and associated employees.
  • Changing the customer or branch handling the repair.

This operation helps maintain accurate and up-to-date repair records, improving workflow efficiency and customer service quality.

Properties

Name Meaning
Repair ID ID of the repair ticket to update (required).
Ticket Type Type of repair ticket; typically 1 for standard tickets (required).
Repair Type Type of repair: either "Single" (one device) or "Multiple" (multiple devices).
Customer ID ID of the customer requesting the repair (required).
Branch ID ID of the branch handling the repair (required).
Device Name Name or model of the device being repaired.
Device Category ID Category ID representing the type of device (required).
Serial Number Serial number of the device.
Lock Screen Key Identifier for the lock screen key (e.g., password type).
Lock Screen Value The actual lock screen password, PIN, or pattern.
Repair Accessories JSON array of accessories related to the repair, e.g., [{"id": "39", "name": "Accessory name"}].
Device States JSON array describing device issues or states, e.g., [{"id": "69", "name": "Issue description"}].
Repair Services JSON array detailing repair services, including pricing, employees involved, and notes. Example structure includes fields like employees, isCustom, serviceId, totalAmount, name, totalChangeAmount, and repairDeliveryNotes.

Output

The output is a JSON object representing the updated repair ticket as returned by the Livo API. It contains all the updated details of the repair, reflecting the changes made through the update operation.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Livo API.
  • The node must be configured with the correct environment URL and API key.
  • The API endpoint used for updating repairs is a PUT request to /api/ecommerce/repairwarrantyticket/{repairId}.

Troubleshooting

  • Common Issues:

    • Invalid or missing Repair ID will cause the update to fail.
    • Malformed JSON in properties like repairAccessorys, repairDeviceStates, or repairServices can cause parsing errors.
    • Incorrect API key or environment URL configuration will result in authentication or connection errors.

  • Error Messages:

    • Errors from the API are passed through; typical messages might indicate invalid IDs, unauthorized access, or validation failures on required fields.
    • To resolve, verify that all required fields are correctly set, JSON arrays are properly formatted, and credentials are valid.

Links and References

Discussion