/**
* Samsara API
* # Overview Something new! 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.
Want to access the legacy API docs? You can find them [here](https://www.samsara.com/api-legacy).
*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!*
Submit your feedback [here](https://forms.gle/r4bs6HQshQAvBuwv6)! 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/ ``` For EU customers, this URL will be: ``` https://api.eu.samsara.com/ ``` Note Legacy endpoints will have the URL: `https://api.samsara.com/v1/` or `https://api.eu.samsara.com/v1/` ## 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.
*/
import { VehicleResponseResponseBody } from './vehicle-response-response-body';
/**
* The metadata of the log.
* @export
* @interface LogMetaDataObjectResponseBody
*/
export interface LogMetaDataObjectResponseBody {
/**
* Whether the driver has claimed the [Adverse Driving Exemption](https://kb.samsara.com/hc/en-us/articles/360047336792-Adverse-Driving-Exemption) for this HOS day chart.
* @type {boolean}
* @memberof LogMetaDataObjectResponseBody
*/
'adverseDrivingClaimed'?: boolean;
/**
* Whether the driver has claimed the [Big Day Exemption](https://kb.samsara.com/hc/en-us/articles/360057113891-16-Hour-Short-Haul-Exemption-Big-Day-) for this HOS day chart.
* @type {boolean}
* @memberof LogMetaDataObjectResponseBody
*/
'bigDayClaimed'?: boolean;
/**
* The address of the carrier used for this HOS chart.
* @type {string}
* @memberof LogMetaDataObjectResponseBody
*/
'carrierFormattedAddress'?: string;
/**
* The name of the carrier used for this HOS chart.
* @type {string}
* @memberof LogMetaDataObjectResponseBody
*/
'carrierName'?: string;
/**
* The US DOT number of the carrier used for this HOS chart.
* @type {number}
* @memberof LogMetaDataObjectResponseBody
*/
'carrierUsDotNumber'?: number;
/**
* The time this log was certified in RFC 3339 format.
* @type {string}
* @memberof LogMetaDataObjectResponseBody
*/
'certifiedAtTime'?: string;
/**
* The address of the Home Terminal used for this HOS chart.
* @type {string}
* @memberof LogMetaDataObjectResponseBody
*/
'homeTerminalFormattedAddress'?: string;
/**
* The name of the Home Terminal used for this HOS chart.
* @type {string}
* @memberof LogMetaDataObjectResponseBody
*/
'homeTerminalName'?: string;
/**
* Whether this HOS day chart was certified by the driver.
* @type {boolean}
* @memberof LogMetaDataObjectResponseBody
*/
'isCertified'?: boolean;
/**
* Whether the driver has the 150 air-mile Short Haul Exemption active for this HOS day chart.
* @type {boolean}
* @memberof LogMetaDataObjectResponseBody
*/
'isUsShortHaulActive'?: boolean;
/**
* List of shipping document names associated with the driver for the day. This field maps to Shipping ID in the dashboard.
* @type {string}
* @memberof LogMetaDataObjectResponseBody
*/
'shippingDocs'?: string;
/**
* List of trailer names associated with the driver for the day. If a trailer was associated with a log through the driver app the trailer name will be the trailer ID.
* @type {Array}
* @memberof LogMetaDataObjectResponseBody
*/
'trailerNames'?: Array;
/**
* List of vehicles associated with the driver for the day.
* @type {Array}
* @memberof LogMetaDataObjectResponseBody
*/
'vehicles'?: Array;
}