ServiceChannel RefrigerantTracking API

The RefrigerantTracking API from ServiceChannel — 49 operation(s) for refrigeranttracking.

Operations 55

GET /refrigeranttracking/ChargeDescriptions Get refrigerant charge descriptions #
GET /refrigeranttracking Get leak tracking preferences #
PUT /refrigeranttracking Update/Insert Leak Tracking Preferences #
POST /refrigeranttracking Get rack equipment #
GET /refrigeranttracking/rack Get Rack Connection #
POST /refrigeranttracking/rack Create/Update Rack Connection #
GET /refrigeranttracking/{locationId}/GetRefrigerantSettings Get Refrigerant settings by locationId #
POST /refrigeranttracking/CheckRefrigerantTrackingAvailable Check if refrigerant tracking is enabled for the location(s) #
POST /refrigeranttracking/CheckRefrigerantTrackingAvailable_v1 Check if refrigerant tracking is enabled for the location(s) #
GET /refrigeranttracking/{subscriberId}/GetRefrigerantUseReasonCodes Get reason codes for refrigerant use #
GET /refrigeranttracking/{assetId}/refrigerantusagesummary Get refrigerant usage summary #
GET /refrigeranttracking/subscribers Get SubscriberIds With RefrigerantTracking Feature Flag #
PUT /refrigeranttracking/leakrecord Complete/update a leak event #
PUT /refrigeranttracking/leakrecordV1 UpdateLeakRecord With Returns Detail Operation Result #
GET /refrigeranttracking/{trackingNumber}/leakRecord Get leak events by `workorderID` #
POST /refrigeranttracking/CreateLeakRecordFollowupWo Creates Follow Up wo for non-closed leak records #
GET /refrigeranttracking/leakRecord/faultCodes Retrieve leak record fault codes #
GET /refrigeranttracking/isRefrigerantTrackingAvailable/{locationId} #
GET /refrigeranttracking/leakRecord/actionCodes Retrieve leak record action codes #
POST /refrigeranttracking/leakNote Add leak note #
GET /refrigeranttracking/{subscriberId}/leaklocations Get leak locations #
GET /refrigeranttracking/leakareas Get leak areas #
POST /refrigeranttracking/addLeakDetectorAudit Add leak detector audit #
GET /refrigeranttracking/getLeakDetectorLastAudit get leak detector last audit #
POST /refrigeranttracking/createChargeHistory Create Charge History #
POST /refrigeranttracking/addUpdateRefrigerationDetails Add Update Refrigeration Details #
POST /refrigeranttracking/AddOrUpdateRefrigerationTypes #
POST /refrigeranttracking/SaveRefrigerationDetails Add/Update Refrigeration Details for an asset #
GET /refrigeranttracking/RefrigerantTypes Get refrigerant types #
GET /refrigeranttracking/LeakVerificationMethods Get Leak Verification Methods #
GET /refrigeranttracking/{assetTypeId}/getRefrigerantUseTypes Get refrigerant use types for equipment #
GET /refrigeranttracking/GetRackTypeListItems Get Rack Type List Items #
GET /refrigeranttracking/OperationalStatuses Get Operational Statuses #
GET /refrigeranttracking/SystemLocations Get physical locations of refrigeration systems #
GET /refrigeranttracking/{workOrderId}/isCompletedStatusesLimitedByRTSetup Check If WO Status Is Limited By RTSetup #
GET /refrigeranttracking/{workOrderId}/checkRefrigerantWasUsedIsValidForInvoiceableStatuses Check If Used Refrigerant Is Valid For Invoiceble Statuses #
POST /refrigeranttracking/{workOrderId}/createLeakRecordFollowUpWoForStatusUpdate Create Leak Record Follow Up WorkOrder #
PUT /refrigeranttracking/WOLeakVerification Update WOLeakVerification #
POST /refrigeranttracking/WOLeakVerification Add WOLeakVerification #
GET /refrigeranttracking/WOLeakVerification/{trackingNumber} Get leak verification methods for EPA Leak Inspection WOs #
PUT /refrigeranttracking/LeakRecordImmeasurable Update a leak record #
POST /refrigeranttracking/LeakRecordImmeasurable Add a leak record to a work order and an asset #
GET /refrigeranttracking/LeakRecordImmeasurable/{trackingNumber} Get leak records by `workorderID` and `assetID` #
DELETE /refrigeranttracking/DeleteLeakRecordImmeasurable Delete a leak record #
GET /refrigeranttracking/leakrecords/{trackingNumber} Get leak events with leak records by `workorderID` #
POST /refrigeranttracking/BulkLeakrecords Update multiple leak records for a work order and an asset #
POST /refrigeranttracking/BulkLeakRecordsAndAudit Update multiple leak records for a work order and an asset #
POST /refrigeranttracking/GetLeakRecordsVerificationHistory Get leak immeasurable verification history #
POST /refrigeranttracking/LeakInspectionComplianceAcknowledgement Add Leak Inspection Compliance Acknowledgement #
GET /refrigeranttracking/MultiAssetLeakInspectionComplianceAcknowledgement Get Leak Inspections Compliance Acknowledgement by trackingNumber and assetId #
POST /refrigeranttracking/MultiAssetLeakInspectionComplianceAcknowledgement Add Leak Inspections Compliance Acknowledgement #
GET /refrigeranttracking/{workOrderId}/isSecondaryLeakVerificationRequired Check if a WO requires secondary leak verification #
DELETE /refrigeranttracking/DeleteRetrofitRetirePlan Delete retrofit/retire plan #
POST /refrigeranttracking/AddRetrofitRetirePlan Add retrofit retire plan #
POST /refrigeranttracking/UpdateRetrofitRetirePlan Update retrofit retire plan #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/servicechannel-refrigeranttracking-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

servicechannel-refrigeranttracking-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: bearer.v1
  title: Fixxbook.Bearer.Api.V1 AfterHours Refrigerant Tracking API
  isOdataApi: false
  relativePath: ''
  discoveryPath: docs/bearer.v1
  _isAuthorizedAccess: true
servers:
- url: https://sb2fixxbook.servicechannel.com:443/api
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.\n            <br />For both subscribers and providers."
      operationId: GETv3_refrigeranttracking_ChargeDescriptions
      responses:
        '200':
          description: The request succeeded, and the charge descriptions are in the response.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceChannel.Services.WebApi.Models.Response.AssetManager.RefrigerantChargeOptionResponseItem'
            text/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceChannel.Services.WebApi.Models.Response.AssetManager.RefrigerantChargeOptionResponseItem'
        '401':
          description: "The requested resource requires authentication.\n            <br/>Error codes:\n            504 — API call rejected by security permissions."
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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. \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}
      parameters:
      - name: subscriberId
        in: query
        description: Unique numeric identifier of the subscriber.
        required: true
        schema:
          type: integer
          format: int32
      responses:
        '200':
          description: Refrigerant tracking settings for the specified subscriber are in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantSettings.RefrigerantSettingsUS'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantSettings.RefrigerantSettingsUS'
        '400':
          description: "The request is not accepted due to bad syntax, missing parameters, insufficient data, etc.\n            <br/>Error codes:           \n            502 &mdash; No refrigerant tracking preferences are found for this subscriber\n            503 &mdash; Invalid subscriber"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "The requested resource requires authentication.\n            <br>Error codes:\n            504 &mdash; API call rejected by security permissions"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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
      responses:
        '200':
          description: Indicates that the request succeeded and that the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/System.Object'
            text/json:
              schema:
                $ref: '#/components/schemas/System.Object'
        '400':
          description: "Bad Request - the request could not be understood or was missing required parameters.\n            <br/>Error codes:            \n            <br/> 502 - No Update/Insert Leak Tracking Preferences;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "Indicates that the requested resource requires authentication.\n            <br>Error codes:\n            <br> 504 - API call rejected by security permissions;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
      deprecated: false
      x-access: Any
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.PreferencesRequest'
          text/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.PreferencesRequest'
        required: true
    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.\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
      responses:
        '200':
          description: Rack assets are returned in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Core.InternalRequests.RefrigerantTracking.GetAvailableRacksResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Core.InternalRequests.RefrigerantTracking.GetAvailableRacksResponse'
        '400':
          description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\n            <br/>Error codes:           \n            502 &mdash; No rack equipment\n            503 &mdash; Request is empty or null"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "The requested resource requires authentication.\n            <br/>Error codes:\n            504 &mdash; API call rejected by security permissions"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
      deprecated: false
      x-access: Any
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.Equipments.GetAvailableRacksRequest'
          text/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.Equipments.GetAvailableRacksRequest'
        description: 'Request for getting a list of rack systems available at the specified location. The required parameters are: `SubscriberId` and `LocationId`.'
        required: true
  /refrigeranttracking/rack:
    get:
      tags:
      - RefrigerantTracking
      summary: Get Rack Connection
      description: Rack Connection
      operationId: GETv3_refrigeranttracking_rack?id={id}
      parameters:
      - name: id
        in: query
        required: true
        schema:
          type: integer
          format: int32
      responses:
        '200':
          description: Indicates that the request succeeded and that the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.GetConnectedRackResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.GetConnectedRackResponse'
        '400':
          description: "Bad Request - the request could not be understood or was missing required parameters.\n            <br/>Error codes:           \n            <br/> 502 - No Get Rack Connection"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "Indicates that the requested resource requires authentication.\n            <br>Error codes:\n            <br> 504 - API call rejected by security permissions;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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
      responses:
        '200':
          description: Indicates that the request succeeded and that the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/System.Object'
            text/json:
              schema:
                $ref: '#/components/schemas/System.Object'
        '400':
          description: "Bad Request - the request could not be understood or was missing required parameters.\n            <br/>Error codes:           \n            <br/> 502 - No Get Rack Connection"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "Indicates that the requested resource requires authentication.\n            <br>Error codes:\n            <br> 504 - API call rejected by security permissions;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
      deprecated: false
      x-access: Any
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.CreateUpdateRackConnectionRequest'
          text/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.CreateUpdateRackConnectionRequest'
        required: true
  /refrigeranttracking/{locationId}/GetRefrigerantSettings:
    get:
      tags:
      - RefrigerantTracking
      summary: Get Refrigerant settings by locationId
      description: GetRefrigerantSettingsByLocationId
      operationId: GETv3_refrigeranttracking_{locationId}_GetRefrigerantSettings
      parameters:
      - name: locationId
        in: path
        description: Location Id
        required: true
        schema:
          type: integer
          format: int32
      responses:
        '200':
          description: Indicates that the request succeeded and that the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.WebApi.Models.Response.RefrigerantSettingsWithFF'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.WebApi.Models.Response.RefrigerantSettingsWithFF'
        '400':
          description: "Bad Request - the request could not be understood or was missing required parameters.\n            <br/>Error codes:           \n            <br/> 502 - No Refrigerant Setings;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "Indicates that the requested resource requires authentication.\n            <br>Error codes:\n            <br> 504 - API call rejected by security permissions;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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
      responses:
        '200':
          description: Request succeeded, and the requested information is in the response.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantSettings.RefrigerantSettingByLocationItem'
            text/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantSettings.RefrigerantSettingByLocationItem'
        '400':
          description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\n            <br/>Error codes:           \n            502 &mdash; No leak tracking preferences"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "The requested resource requires authentication.\n            <br/>Error codes:\n            504 &mdash; API call rejected by security permissions"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
      deprecated: false
      x-access: Any
      requestBody:
        content:
          application/json:
            schema:
              type: array
              items:
                format: int32
                type: integer
          text/json:
            schema:
              type: array
              items:
                format: int32
                type: integer
        description: "Unique numeric identifier of the location (generated by the system). To get a location ID, run either of the methods:\n             • `GET/stores`\n             • `GET/locations`\n            <br />Separate multiple locations’ IDs with a comma."
        required: true
  /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:\n             • `0`: Pounds and decimals of pounds\n             • `1`: Pounds and ounces\n             • `2`: Kilograms and grams"
      operationId: POSTv3_refrigeranttracking_CheckRefrigerantTrackingAvailable_v1
      responses:
        '200':
          description: Request succeeded, and the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/System.Object'
            text/json:
              schema:
                $ref: '#/components/schemas/System.Object'
        '400':
          description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\n            <br/>Error codes:           \n            502 &mdash; No leak tracking preferences"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "The requested resource requires authentication.\n            <br/>Error codes:\n            504 &mdash; API call rejected by security permissions"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '500':
          description: "Something went wrong, and the server was unable to complete your request.\n            <br/>Error codes:\n            501 &mdash; Internal error"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
      deprecated: false
      x-access: Any
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Core.InternalRequests.RefrigerantTracking.CheckRefrigerantTrackingRequest'
          text/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Core.InternalRequests.RefrigerantTracking.CheckRefrigerantTrackingRequest'
        description: "Request containing a list of location IDs (unique numeric identifiers, generated by the system). To get location IDs, run either of the methods:\n             • `GET/stores`\n             • `GET/locations`"
        required: true
  /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
      parameters:
      - name: subscriberId
        in: path
        description: Unique numeric identifier of the subscriber.
        required: true
        schema:
          type: integer
          format: int32
      responses:
        '200':
          description: The list of reason codes is in the response.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantUseReasonCode'
            text/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.RefrigerantUseReasonCode'
        '400':
          description: "The request was not accepted due to bad syntax, missing parameters, insufficient data, etc.\n            <br/>Error codes:           \n            502 &mdash; No leak tracking preferences"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "The requested resource requires authentication.\n            <br/>Error codes:\n            504 &mdash; API call rejected by security permissions"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '404':
          description: The requested resource does not exist on the server.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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
      parameters:
      - name: assetId
        in: path
        description: ''
        required: true
        schema:
          type: integer
          format: int32
      responses:
        '200':
          description: Indicates that the request succeeded and that the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/System.Object'
            text/json:
              schema:
                $ref: '#/components/schemas/System.Object'
        '400':
          description: "Bad Request - the request could not be understood or was missing required parameters.\n            <br/>Error codes:            \n            <br/> 502 - No Update/Insert Leak Tracking Preferences;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "Indicates that the requested resource requires authentication.\n            <br>Error codes:\n            <br> 504 - API call rejected by security permissions;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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
      responses:
        '200':
          description: Indicates that the request succeeded and that the requested information is in the response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/System.Object'
            text/json:
              schema:
                $ref: '#/components/schemas/System.Object'
        '400':
          description: "Bad Request - the request could not be understood or was missing required parameters.\n            <br/>Error codes:            \n            <br/> 502 - No Update/Insert Leak Tracking Preferences;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "Indicates that the requested resource requires authentication.\n            <br>Error codes:\n            <br> 504 - API call rejected by security permissions;"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/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. \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
      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.\n            <br/>Error codes:            \n            502 &mdash; Leak record was not updated\n            503 &mdash; Leak location ID is required\n            503 &mdash; Leak record is not found\n            503 &mdash; 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.\n            503 &mdash; Completion date can't be less than the leak record repair date\n            503 &mdash; Completion date can't be less than the work order call date\n            503 &mdash; Completion date can't be more than the work order completion date\n            503 &mdash; Follow-up date and the completed date can't be earlier than the initial date\n            503 &mdash; Follow-up date and the completed date can't be earlier than the repair date\n            503 &mdash; Follow-up date and the completed date can't be earlier than the trigger date\n            503 &mdash; Repair date and the initial date should be entered\n            503 &mdash; Repair date is required\n            503 &mdash; Follow-up verification date and/or the completed date is earlier than the refrigerant removal date\n            503 &mdash; Repair date and the completion date can't be earlier than the work order call date\n            503 &mdash; Repair date and the completion date can't be more than the work order completion date \n            503 &mdash; Leak record completion date cannot be less than the refrigerant usage date\n            503 &mdash; Leak record repair and the verification date should be less than the next leak record triggered date\n            503 &mdash; Leak record initial date should be less than the next leak record triggered date\n            503 &mdash; Leak record repair and the verification date should be less than any refrigerant use related to the next leak record\n            503 &mdash; Leak record repair and the verification date should be more than the previous leak record completion date\n            503 &mdash; Initial date can't be earlier than the repair date\n            503 &mdash; Leak record completion date should not be out of the retrofit plan dates\n            503 &mdash; Work order is in the completed status. Only RT Admins can process\n            503 &mdash; Work order is already completed. Verification data cannot be removed\n            503 &mdash; Follow-up date must equal the completed date\n            503 &mdash; Leak event should contain at least one leak record"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '401':
          description: "The requested resource requires authentication. \n            <br>Error codes:\n            504 &mdash; API call rejected by security permissions"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
        '500':
          description: "Something went wrong, and the server was unable to complete your request.\n            <br>Error codes:\n            501 &mdash; Internal Error"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/ServiceChannel.Services.Messaging.ErrorResponse'
      deprecated: false
      x-access: Any
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.UpdateLeakRecordRequest'
          text/json:
            schema:
              $ref: '#/components/schemas/ServiceChannel.Services.Messaging.RefrigerantTracking.UpdateLeakRecordRequest'
        description: "Request model to update a leak event. \n            <br />***Note:*** When the *RTMultiLeakFlow* FF is on, you can send the request with two parameters only: `Id` and `CompletedDate`.\n            \n            {\n              \"Id\": 1152

# --- truncated at 32 KB (248 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/servicechannel/refs/heads/main/openapi/servicechannel-refrigeranttracking-api-openapi.yml