ServiceChannel RefrigerantTracking API
The RefrigerantTracking API from ServiceChannel — 49 operation(s) for refrigeranttracking.
OpenAPI Specification
swagger: '2.0'
info:
version: bearer.v1
title: Fixxbook.Bearer.Api.V1 AfterHours RefrigerantTracking API
isOdataApi: false
relativePath: ''
discoveryPath: docs/bearer.v1
_isAuthorizedAccess: true
host: sb2fixxbook.servicechannel.com:443
basePath: /api
schemes:
- https
security:
- oauth2: []
tags:
- name: RefrigerantTracking
paths:
/refrigeranttracking/ChargeDescriptions:
get:
tags:
- RefrigerantTracking
summary: Get refrigerant charge descriptions
description: "Shows a list of refrigerant charge descriptions and their IDs. Charge descriptions represent different methods of adding the refrigerant to a system. The descriptions are universal and available to users upon adding a charge record for a refrigerated asset.\r\n <br />For both subscribers and providers."
operationId: GETv3_refrigeranttracking_ChargeDescriptions
consumes: []
produces:
- application/json
- text/json
responses:
'200':
description: The request succeeded, and the charge descriptions are in the response.
schema:
type: array
items:
$ref: '#/definitions/ServiceChannel.Services.WebApi.Models.Response.AssetManager.RefrigerantChargeOptionResponseItem'
'401':
description: "The requested resource requires authentication.\r\n <br/>Error codes:\r\n 504 — API call rejected by security permissions."
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking:
get:
tags:
- RefrigerantTracking
summary: Get leak tracking preferences
description: "Shows refrigerant leak tracking preferences, including Commercial Refrigerant Trigger Rate, HVAC Trigger Rate, PM Leak Inspection NTE, and more, configured for the subscriber. \r\n <br />When the *RefrigerationTracking* feature flag is turned off for the subscriber, the method returns the default — EPA standard — values."
operationId: GETv3_refrigeranttracking?subscriberId={subscriberId}
consumes: []
produces:
- application/json
- text/json
parameters:
- name: subscriberId
in: query
description: Unique numeric identifier of the subscriber.
required: true
type: integer
format: int32
responses:
'200':
description: Refrigerant tracking settings for the specified subscriber are in the response.
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantSettings.RefrigerantSettingsUS'
'400':
description: "The request is not accepted due to bad syntax, missing parameters, insufficient data, etc.\r\n <br/>Error codes: \r\n 502 — No refrigerant tracking preferences are found for this subscriber\r\n 503 — Invalid subscriber"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "The requested resource requires authentication.\r\n <br>Error codes:\r\n 504 — API call rejected by security permissions"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
put:
tags:
- RefrigerantTracking
summary: Update/Insert Leak Tracking Preferences
description: Update/Insert Leak Tracking Preferences. Returns Success/NoSuccess request.
operationId: PUTv3_refrigeranttracking
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
description: ''
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.PreferencesRequest'
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update/Insert Leak Tracking Preferences;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
post:
tags:
- RefrigerantTracking
summary: Get rack equipment
description: "Returns rack assets for the specified subscriber and location. Only assets with the **Refrigerant Usage Type** set to **Rack** will be sent in the response.\r\n <br />To check the rack connection, use the [GET/refrigeranttracking/rack](https://developer.servicechannel.com/swagger/index.html#/RefrigerantTracking/GETv3_refrigeranttracking_rack%3Fid%3D%7Bid%7D) method."
operationId: POSTv3_refrigeranttracking
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
description: 'Request for getting a list of rack systems available at the specified location. The required parameters are: `SubscriberId` and `LocationId`.'
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.Equipments.GetAvailableRacksRequest'
responses:
'200':
description: Rack assets are returned in the response.
schema:
$ref: '#/definitions/ServiceChannel.Services.Core.InternalRequests.RefrigerantTracking.GetAvailableRacksResponse'
'400':
description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\r\n <br/>Error codes: \r\n 502 — No rack equipment\r\n 503 — Request is empty or null"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "The requested resource requires authentication.\r\n <br/>Error codes:\r\n 504 — API call rejected by security permissions"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/rack:
get:
tags:
- RefrigerantTracking
summary: Get Rack Connection
description: Rack Connection
operationId: GETv3_refrigeranttracking_rack?id={id}
consumes: []
produces:
- application/json
- text/json
parameters:
- name: id
in: query
required: true
type: integer
format: int32
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.GetConnectedRackResponse'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Get Rack Connection"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
post:
tags:
- RefrigerantTracking
summary: Create/Update Rack Connection
description: Create/Update Rack Connection
operationId: POSTv3_refrigeranttracking_rack
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.CreateUpdateRackConnectionRequest'
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Get Rack Connection"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/{locationId}/GetRefrigerantSettings:
get:
tags:
- RefrigerantTracking
summary: Get Refrigerant settings by locationId
description: GetRefrigerantSettingsByLocationId
operationId: GETv3_refrigeranttracking_{locationId}_GetRefrigerantSettings
consumes: []
produces:
- application/json
- text/json
parameters:
- name: locationId
in: path
description: Location Id
required: true
type: integer
format: int32
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/ServiceChannel.Services.WebApi.Models.Response.RefrigerantSettingsWithFF'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Refrigerant Setings;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/CheckRefrigerantTrackingAvailable:
post:
tags:
- RefrigerantTracking
summary: Check if refrigerant tracking is enabled for the location(s)
description: Verifies whether the refrigerant tracking settings are enabled for the specified location(s).
operationId: POSTv3_refrigeranttracking_CheckRefrigerantTrackingAvailable
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: locationIds
in: body
description: "Unique numeric identifier of the location (generated by the system). To get a location ID, run either of the methods:\r\n • `GET/stores`\r\n • `GET/locations`\r\n <br />Separate multiple locations’ IDs with a comma."
required: true
schema:
type: array
items:
format: int32
type: integer
responses:
'200':
description: Request succeeded, and the requested information is in the response.
schema:
type: array
items:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantSettings.RefrigerantSettingByLocationItem'
'400':
description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\r\n <br/>Error codes: \r\n 502 — No leak tracking preferences"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "The requested resource requires authentication.\r\n <br/>Error codes:\r\n 504 — API call rejected by security permissions"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/CheckRefrigerantTrackingAvailable_v1:
post:
tags:
- RefrigerantTracking
summary: Check if refrigerant tracking is enabled for the location(s)
description: "Verifies whether the refrigerant tracking settings are enabled for the specified location(s). Additionally, returns the unit of measure for each location:\r\n • `0`: Pounds and decimals of pounds\r\n • `1`: Pounds and ounces\r\n • `2`: Kilograms and grams"
operationId: POSTv3_refrigeranttracking_CheckRefrigerantTrackingAvailable_v1
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
description: "Request containing a list of location IDs (unique numeric identifiers, generated by the system). To get location IDs, run either of the methods:\r\n • `GET/stores`\r\n • `GET/locations`"
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Core.InternalRequests.RefrigerantTracking.CheckRefrigerantTrackingRequest'
responses:
'200':
description: Request succeeded, and the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\r\n <br/>Error codes: \r\n 502 — No leak tracking preferences"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "The requested resource requires authentication.\r\n <br/>Error codes:\r\n 504 — API call rejected by security permissions"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'500':
description: "Something went wrong, and the server was unable to complete your request.\r\n <br/>Error codes:\r\n 501 — Internal error"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/{subscriberId}/GetRefrigerantUseReasonCodes:
get:
tags:
- RefrigerantTracking
summary: Get reason codes for refrigerant use
description: Retrieves a list of reason codes for the refrigerant part use. For example, leak or repair.
operationId: GETv3_refrigeranttracking_{subscriberId}_GetRefrigerantUseReasonCodes
consumes: []
produces:
- application/json
- text/json
parameters:
- name: subscriberId
in: path
description: Unique numeric identifier of the subscriber.
required: true
type: integer
format: int32
responses:
'200':
description: The list of reason codes is in the response.
schema:
type: array
items:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantUseReasonCode'
'400':
description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\r\n <br/>Error codes: \r\n 502 — No leak tracking preferences"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "The requested resource requires authentication.\r\n <br/>Error codes:\r\n 504 — API call rejected by security permissions"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'404':
description: The requested resource does not exist on the server.
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/{assetId}/refrigerantusagesummary:
get:
tags:
- RefrigerantTracking
summary: Get refrigerant usage summary
operationId: GETv3_refrigeranttracking_{assetId}_refrigerantusagesummary
consumes: []
produces:
- application/json
- text/json
parameters:
- name: assetId
in: path
description: ''
required: true
type: integer
format: int32
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update/Insert Leak Tracking Preferences;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/subscribers:
get:
tags:
- RefrigerantTracking
summary: Get SubscriberIds With RefrigerantTracking Feature Flag
operationId: GETv3_refrigeranttracking_subscribers
consumes: []
produces:
- application/json
- text/json
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update/Insert Leak Tracking Preferences;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/leakrecord:
put:
tags:
- RefrigerantTracking
summary: Complete/update a leak event
description: "Allows users to close a leak event by setting the completion date. Other leak information can be updated as well for both in-progress and completed leak events. \r\n <br />***Note:*** When the *RTMultiLeakFlow* feature flag is on, you can only add or update the completion date via this method. Other parameters cannot be modified. Note that at least one leak record should be associated with the event."
operationId: PUTv3_refrigeranttracking_leakrecord
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
description: "Request model to update a leak event. \r\n <br />***Note:*** When the *RTMultiLeakFlow* FF is on, you can send the request with two parameters only: `Id` and `CompletedDate`.\r\n \r\n {\r\n \"Id\": 115264,\r\n \"CompletedDate\": \"2023-10-12T15:16:19.178Z\"\r\n }"
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.UpdateLeakRecordRequest'
responses:
'200':
description: The specified leak event has been successfully updated.
'400':
description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\r\n <br/>Error codes: \r\n 502 — Leak record was not updated\r\n 503 — Leak location ID is required\r\n 503 — Leak record is not found\r\n 503 — Follow-up verification date on the leak record cannot be less than the initial verification date + secondary verification delay time. Depending on the refrigerant tracking settings, it could be required to pass the follow-up verification not earlier than in several days after the initial verification.\r\n 503 — Completion date can't be less than the leak record repair date\r\n 503 — Completion date can't be less than the work order call date\r\n 503 — Completion date can't be more than the work order completion date\r\n 503 — Follow-up date and the completed date can't be earlier than the initial date\r\n 503 — Follow-up date and the completed date can't be earlier than the repair date\r\n 503 — Follow-up date and the completed date can't be earlier than the trigger date\r\n 503 — Repair date and the initial date should be entered\r\n 503 — Repair date is required\r\n 503 — Follow-up verification date and/or the completed date is earlier than the refrigerant removal date\r\n 503 — Repair date and the completion date can't be earlier than the work order call date\r\n 503 — Repair date and the completion date can't be more than the work order completion date \r\n 503 — Leak record completion date cannot be less than the refrigerant usage date\r\n 503 — Leak record repair and the verification date should be less than the next leak record triggered date\r\n 503 — Leak record initial date should be less than the next leak record triggered date\r\n 503 — Leak record repair and the verification date should be less than any refrigerant use related to the next leak record\r\n 503 — Leak record repair and the verification date should be more than the previous leak record completion date\r\n 503 — Initial date can't be earlier than the repair date\r\n 503 — Leak record completion date should not be out of the retrofit plan dates\r\n 503 — Work order is in the completed status. Only RT Admins can process\r\n 503 — Work order is already completed. Verification data cannot be removed\r\n 503 — Follow-up date must equal the completed date\r\n 503 — Leak event should contain at least one leak record"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "The requested resource requires authentication. \r\n <br>Error codes:\r\n 504 — API call rejected by security permissions"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'500':
description: "Something went wrong, and the server was unable to complete your request.\r\n <br>Error codes:\r\n 501 — Internal Error"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/leakrecordV1:
put:
tags:
- RefrigerantTracking
summary: UpdateLeakRecord With Returns Detail Operation Result
operationId: PUTv3_refrigeranttracking_leakrecordV1
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
description: ''
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.UpdateLeakRecordRequest'
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update Leak Record;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/{trackingNumber}/leakRecord:
get:
tags:
- RefrigerantTracking
summary: Get leak events by `workorderID`
description: Returns [leak events](https://servicechannel.atlassian.net/wiki/spaces/SCU/pages/573898951/Viewing+Refrigerant+Leak+Events) generated on the certain work order and associated leak records.
operationId: GETv3_refrigeranttracking_{trackingNumber}_leakRecord
consumes: []
produces:
- application/json
- text/json
parameters:
- name: trackingNumber
in: path
description: Unique numeric identifier of the work order.
required: true
type: integer
format: int32
responses:
'200':
description: The request succeeded and the requested information is in the response.
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.AssetLeakHistoryResponse'
'401':
description: "The request is not authorized.\r\n <br/> Error codes:\r\n 504 — API call rejected by security permissions"
deprecated: false
x-access: Any
/refrigeranttracking/CreateLeakRecordFollowupWo:
post:
tags:
- RefrigerantTracking
summary: Creates Follow Up wo for non-closed leak records
operationId: POSTv3_refrigeranttracking_CreateLeakRecordFollowupWo?leakRecordId={leakRecordId}¤tTrackingNumber={currentTrackingNumber}
consumes: []
produces:
- application/json
- text/json
parameters:
- name: leakRecordId
in: query
description: ''
required: true
type: integer
format: int32
- name: currentTrackingNumber
in: query
description: ''
required: true
type: integer
format: int32
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update/Insert Leak Tracking Preferences;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/leakRecord/faultCodes:
get:
tags:
- RefrigerantTracking
summary: Retrieve leak record fault codes
operationId: GETv3_refrigeranttracking_leakRecord_faultCodes
consumes: []
produces:
- application/json
- text/json
responses:
'200':
description: OK
schema:
$ref: '#/definitions/System.Object'
deprecated: false
x-access: Any
/refrigeranttracking/isRefrigerantTrackingAvailable/{locationId}:
get:
tags:
- RefrigerantTracking
operationId: GETv3_refrigeranttracking_isRefrigerantTrackingAvailable_{locationId}
consumes: []
produces:
- application/json
- text/json
parameters:
- name: locationId
in: path
required: true
type: integer
format: int32
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update/Insert Leak Tracking Preferences;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/leakRecord/actionCodes:
get:
tags:
- RefrigerantTracking
summary: Retrieve leak record action codes
operationId: GETv3_refrigeranttracking_leakRecord_actionCodes
consumes: []
produces:
- application/json
- text/json
responses:
'200':
description: OK
schema:
$ref: '#/definitions/System.Object'
deprecated: false
x-access: Any
/refrigeranttracking/leakNote:
post:
tags:
- RefrigerantTracking
summary: Add leak note
operationId: POSTv3_refrigeranttracking_leakNote
consumes:
- application/json
- text/json
produces:
- application/json
- text/json
parameters:
- name: request
in: body
description: ''
required: true
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.RefrigerantTracking.AddLeakNoteRequest'
responses:
'200':
description: Indicates that the request succeeded and that the requested information is in the response.
schema:
$ref: '#/definitions/System.Object'
'400':
description: "Bad Request - the request could not be understood or was missing required parameters.\r\n <br/>Error codes: \r\n <br/> 502 - No Update/Insert Leak Tracking Preferences;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
'401':
description: "Indicates that the requested resource requires authentication.\r\n <br>Error codes:\r\n <br> 504 - API call rejected by security permissions;"
schema:
$ref: '#/definitions/ServiceChannel.Services.Messaging.ErrorResponse'
deprecated: false
x-access: Any
/refrigeranttracking/{subscriberId}/leaklocations:
get:
tags:
- RefrigerantTracking
summary: Get leak locations
# --- truncated at 32 KB (217 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/servicechannel/refs/heads/main/openapi/servicechannel-refrigeranttracking-api-openapi.yml