---
title: "UpdateLeakRecord With Returns Detail Operation Result"
method: PUT
path: "/refrigeranttracking/leakrecordV1"
tags: ["RefrigerantTracking"]
---

# UpdateLeakRecord With Returns Detail Operation Result

`PUT /refrigeranttracking/leakrecordV1`

## Request

- Base URL: `https://sb2api.servicechannel.com/v3`
- URL: `https://sb2api.servicechannel.com/v3/refrigeranttracking/leakrecordV1`
- Auth: OAuth 2
  - Authorization code: `https://sb2login.servicechannel.com/oauth/authorize`
  - Token URL: `https://sb2login.servicechannel.com/oauth/token`
- TypeScript: <https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3/docs/refrigeranttracking/leakrecordV1/put.ts> (a function with typed inputs; its response is checked against the schema)

## Request body

- ServiceChannelServicesMessagingRefrigerantTrackingUpdateLeakRecordRequest: Object containing information about the leak event.
  - `Id` integer, required: Unique numeric identifier of the leak event. Leak event IDs can be found in the **Refrigerant Leak Events** report in Service Automation.
  - `Note` string: Leak record note.
  - `RepairDate` string, date-time: Date when the repair was completed. It cannot be earlier than the work order call date. The date format is `YYYY-MM-DDThh:mm:ss.sssZ`.
  - `InitialDate` string, date-time: Date when the first leak verification took place. The date format is `YYYY-MM-DDThh:mm:ss.sssZ`. ***Note:*** The initial verification date cannot be in the future. It should be either a current date or a date in the past.
  - `InitialMethod` integer: Method that was used during the first verification to make sure the leak had been fixed. <br />Possible values: • `0`: Unknown • `1`: Soap Bubble Test • `2`: Electronic Leak Detection • `3`: Ultrasonic Leak Detection • `4`: Pressure Test • `5`: Vacuum Test • `6`: Fluorescent Dye Test • `7`: Infrared Test • `8`: Near Infrared Test • `9`: Halon Gas Detection
  - `FollowUpDate` string, date-time: Date of the second verification. The date format is `YYYY-MM-DDThh:mm:ss.sssZ`. ***Note:*** The follow-up verification date cannot be earlier than the initial verification date and cannot be in the future. It should be either a current date or a date in the past.
  - `FollowUpMethod` integer: Method of the second verification. The list of available verification methods is the same as for the `InitialMethod`.
  - `LeakLocationId` integer: Unique numeric identifier of the location where the leak occurred: more specific place within the particular area, for example, *Level Indicator/Alarm*, *Splitting Valve*. Use the [GET/refrigeranttracking/{subscriberId}/leaklocations](https://developer.servicechannel.com/swagger/index.html#/RefrigerantTracking/GETv3_refrigeranttracking_%7BsubscriberId%7D_leaklocations) method to get the list of available leak locations.
  - `FaultCodeId` integer: Unique numeric identifier of the reason why the problem occurred. Use the [GET/refrigeranttracking/leakRecord/faultCodes](https://developer.servicechannel.com/swagger/index.html#/RefrigerantTracking/GETv3_refrigeranttracking_leakRecord_faultCodes) method to get available fault codes and their IDs. <br />Possible values: • `1`: Accidental Damage • `2`: Braze or Joint Failure • `3`: Corrosion • `4`: Defrost Heater Failure • `5`: Faulty Part • `6`: Forklift Damage • `7`: Gasket Seal Failure • `8`: Ice Build Up • `9`: Line Break • `10`: Manufacture Defect • `11`: Missing Part • `12`: Natural Disaster • `13`: Normal Mechanical Wear • `14`: Other(Must Explain in Comments) • `15`: Vandalism • `16`: Vibration Related • `17`: Project Related Loss
  - `ActionCodeId` integer: Unique numeric identifier of the action that a technician took to fix the leak. Use the [GET/refrigeranttracking/leakRecord/actionCodes](https://developer.servicechannel.com/swagger/index.html#/RefrigerantTracking/GETv3_refrigeranttracking_leakRecord_actionCodes) method to get available action codes and their IDs.
  - `LeakAreaId` integer: Unique numeric identifier of the area where the leak occurred: more general place, for example, *Receiver* or *Compressor*. Use the [GET/refrigeranttracking/leakareas](https://developer.servicechannel.com/swagger/index.html#/RefrigerantTracking/GETv3_refrigeranttracking_leakareas) method to get leak areas and their IDs.
  - `CurrentTrackingNumber` integer: Unique numeric identifier of the work order.
  - `CompletedDate` string, date-time: Date and time when the leak event was completed. The date format is `YYYY-MM-DDThh:mm:ss.sssZ`. ***Note:*** The leak event completion date cannot be earlier than the leak event repair date and later than the work order completion date.

## Response `200`

Indicates that the request succeeded and that the requested information is in the response.

- SystemObject

## Other responses

- `400`: Bad Request - the request could not be understood or was missing required parameters. <br/>Error codes: <br/> 502 - No Update Leak Record;
- `401`: Indicates that the requested resource requires authentication. <br>Error codes: <br> 504 - API call rejected by security permissions;

---

[API](https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3.md) - [All operations](https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3/llms.txt) - [OpenAPI document](https://skmtc.dev/servicechannel/apis/servicechannel-api-v-3/revisions/d490d6596809?raw)