/**
 * Samsara API
 * <style type=\"text/css\"> n {     padding: 1em;     width: 100%;     display: block;     margin: 28px 0; } n.info {     background-color: rgba(0, 51, 160, 0.1); } n.warning {     background-color: #fdf6e3; } i:before {     margin-right: 6px; } nh {     font-size: 1.5rem;     font-weight: 700;     line-height: 1.1;     display: block; } nb {     margin-top: 10px;     padding-left: 22px;     display: block; } </style>  # Overview  <n class=\"info\"> <nh> <i class=\"fa fa-info-circle\"></i> Something new! </nh> <nb> Welcome Samsara\'s new and improved API. Check out our FAQ [here](https://developers.samsara.com/docs/introducing-our-next-generation-api) to see what\'s changed and learn how to get started.<br> <br> Want to access the legacy API docs? You can find them [here](https://www.samsara.com/api-legacy).<br> <br> *Note: Because this is a new set of APIs, we have not transitioned all endpoints over to this standard. Endpoints that still use the legacy standards are indicated in the reference documentation. If you can\'t find an API that you\'re looking for, we encourage you to look for it in our [legacy API docs](https://www.samsara.com/api-legacy) as we continue to transition all endpoints over. Check back here for updates!*<br> <br> Submit your feedback [here](https://forms.gle/r4bs6HQshQAvBuwv6)! </nb> </n>  Samsara provides API endpoints so that you can build powerful applications and custom solutions with sensor data. Samsara has endpoints available to track and analyze sensors, vehicles, and entire fleets.  The Samsara API is a [RESTful API](https://en.wikipedia.org/wiki/Representational_state_transfer). It uses standard [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol) authentication, verbs, and response codes, and it returns [JSON](http://www.json.org/) response bodies. If you\'re familiar with what you can build with a REST API, then this will be your go-to API reference.  Visit [developers.samsara.com](https://developers.samsara.com) to find getting started guides and an API overview.  If you have any questions, please visit https://samsara.com/help.  ## Endpoints  All our APIs can be accessed through HTTP requests to URLs like:  ``` https://api.samsara.com/<endpoint> ```  For EU customers, this URL will be:  ``` https://api.eu.samsara.com/<endpoint> ```  <n class=\"warning\"> <nh> <i class=\"fa fa-exclamation-circle\"></i> Note </nh> <nb> Legacy endpoints will have the URL: `https://api.samsara.com/v1/<endpoint>` or `https://api.eu.samsara.com/v1/<endpoint>` </nb> </n>  ## Authentication  To authenticate your API request you will need to include your secret token. You can manage your API tokens in the [Dashboard](https://cloud.samsara.com). They are visible under `Settings->Organization->API Tokens`.  Your API tokens carry many privileges, so be sure to keep them secure. Do not share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so on.  Authentication to the API is performed via Bearer Token in the HTTP Authorization header. Provide your API token as the `access_token` value in an `Authorization: Bearer` header. You do not need to provide a password:  ```curl Authorization: Bearer {access_token} ```  All API requests must be made over [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP or without authentication will fail.  ### OAuth2 If building an application for our marketplace, our API is accessible via. OAuth2 as well.  | Type  | Value | | ------------- |:-------------:| | Security scheme      | OAuth2                                   | | OAuth2 Flow          | accessCode                               | | Authorization URL    | https://api.samsara.com/oauth2/authorize | | Token URL            | https://api.samsara.com/oauth2/token     |    ## Common Patterns  You can find more info about request methods, response codes, error codes, versioning, pagination, timestamps, and mini-objects [here](https://developers.samsara.com/docs/common-structures).
 *
 * The version of the OpenAPI document: 2024-11-18
 *
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */
/**
 * Representation of a vehicle trailer or other equipment to be tracked.
 * @export
 * @interface AssetsCreateAssetRequestBody
 */
export interface AssetsCreateAssetRequestBody {
    /**
     * A map of external ids
     * @type {{ [key: string]: string; }}
     * @memberof AssetsCreateAssetRequestBody
     */
    'externalIds'?: {
        [key: string]: string;
    };
    /**
     * The license plate of the asset.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'licensePlate'?: string;
    /**
     * The OEM/manufacturer of the asset. Updates to this field are restricted.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'make'?: string;
    /**
     * The model of the asset. Updates to this field are restricted.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'model'?: string;
    /**
     * The human-readable name of the asset. This is set by a fleet administrator and will appear in both Samsara’s cloud dashboard as well as the Samsara Driver mobile app. By default, this name is the serial number of the Samsara Asset Gateway. It can be set or updated through the Samsara Dashboard or through the API at any time.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'name'?: string;
    /**
     * These are generic notes about the asset. Can be set or updated through the Samsara Dashboard or the API at any time.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'notes'?: string;
    /**
     * Whether or not the asset is regulated, unregulated (non-CMV), or a mixed use unregulated asset. Primarily used with vehicles.  Valid values: `mixed`, `regulated`, `unregulated`
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'regulationMode'?: AssetsCreateAssetRequestBodyRegulationModeEnum;
    /**
     * The serial number of the asset. This can be an internal serial number or used to hold legacy VIN/PIN numbers such as ones of shorter lengths.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'serialNumber'?: string;
    /**
     * The operational context in which the asset interacts with the Samsara system. Examples: Vehicle (eg: truck, bus...), Trailer (eg: dry van, reefer, flatbed...), Powered Equipment (eg: dozer, crane...), Unpowered Equipment (eg: container, dumpster...), or Uncategorized.  Valid values: `uncategorized`, `trailer`, `equipment`, `unpowered`, `vehicle`
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'type'?: AssetsCreateAssetRequestBodyTypeEnum;
    /**
     * The unique 17-digit VIN (Vehicle Identification Number) or PIN (Product Identification Number) of the asset.
     * @type {string}
     * @memberof AssetsCreateAssetRequestBody
     */
    'vin'?: string;
    /**
     * The model year of the asset. Updates to this field are restricted.
     * @type {number}
     * @memberof AssetsCreateAssetRequestBody
     */
    'year'?: number;
}
export declare const AssetsCreateAssetRequestBodyRegulationModeEnum: {
    readonly Mixed: "mixed";
    readonly Regulated: "regulated";
    readonly Unregulated: "unregulated";
};
export type AssetsCreateAssetRequestBodyRegulationModeEnum = typeof AssetsCreateAssetRequestBodyRegulationModeEnum[keyof typeof AssetsCreateAssetRequestBodyRegulationModeEnum];
export declare const AssetsCreateAssetRequestBodyTypeEnum: {
    readonly Uncategorized: "uncategorized";
    readonly Trailer: "trailer";
    readonly Equipment: "equipment";
    readonly Unpowered: "unpowered";
    readonly Vehicle: "vehicle";
};
export type AssetsCreateAssetRequestBodyTypeEnum = typeof AssetsCreateAssetRequestBodyTypeEnum[keyof typeof AssetsCreateAssetRequestBodyTypeEnum];