import { BaseClient, RequestOptions } from './base-client'; import { DeviceTypeListResponse, DeviceTypeResponse, DeviceTypeUpdateRequest, DeviceTypeCreateRequest } from './model'; /** * Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the API and offers examples of usage. The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice. The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json) * @class DeviceTypesClient * @param {(string)} [url] - The URL of the API endpoint. */ export declare class DeviceTypesClient extends BaseClient { /** * Retrieve a list of device types for a specified owner. * @method * @name DeviceTypesClient#listDeviceTypes * @param {string} owner - The owner id you are requesting data for * @param {boolean} recurse - Load items from the parent company tree as well (defaults to "true") * @param {number} offset - An offset into the result set, useful for pagination * @param {number} limit - Limit the number of results to this value. * @param {string} sort - Sorting column or attribute name with an optional direction, e.g. `sort=name:desc` * @param {string} filter - A filter to apply to the data in RQL format. */ listDeviceTypes(owner: string, recurse?: boolean, offset?: number, limit?: number, sort?: string, filter?: string, $options?: RequestOptions): Promise; /** * Creates a new device type entity * @method * @name DeviceTypesClient#createDeviceType * @param {object} request - Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the API and offers examples of usage. The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice. The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json) */ createDeviceType(request: DeviceTypeCreateRequest, $options?: RequestOptions): Promise; /** * Returns device type details for the specified id * @method * @name DeviceTypesClient#getDeviceType * @param {string} id - The UUID of the device * @param {string} owner - The optional UUID of a Client. The device type may be customized based on settings and features in the client. */ getDeviceType(id: string, owner?: string, $options?: RequestOptions): Promise; /** * Updates an existing device type * @method * @name DeviceTypesClient#updateDeviceType * @param {string} id - Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the API and offers examples of usage. The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice. The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json) * @param {object} request - Welcome to the Key Telematics Fleet API specification. This document outlines the REST routes and data structures returned by the API and offers examples of usage. The API publishes a [swagger](https://swagger.io/) specification that can be used to [generate a client library](https://github.com/swagger-api/swagger-codegen) for your language of choice. The latest swagger file is available for download from the following link: [https://api.eu1.kt1.io/fleet/v2/swagger.json](https://api.eu1.kt1.io/fleet/v2/swagger.json) */ updateDeviceType(id: string, request: DeviceTypeUpdateRequest, $options?: RequestOptions): Promise; }