Updates information in the specified vehicle profile. Note that all fields are optional, i.e., a partial view of the request body may be given.
Note that the API key has to be sent as Token 123 where 123 is
the key you received after logging in or by creating on the developer
dashboard.
ID of vehicle to update.
Request body when updating a vehicle profile.
The drivetrain of this vehicle.
GASOLINE, DIESEL, ELECTRIC The Bluetooth address of this device. This can (usually) only be set once, after which it is read-only.
The owner-given name of this vehicle.
The brand of this vehicle.
A type description of this vehicle.
The owner-given description of his / her vehicle. -> Deprecated as of v2.1 in favor of description.
The owner-given description of his / her vehicle.
The ID of the "vehicle profile" image. You can retrieve a new image identifier by POSTing a new image to /image/. Please refer to the respective section of this documentation.
The ID of the primary organization, if any. The primary organization is responsible for the subscriptions and payments of the vehicle.
The ID of the manufacturing organization, if any.
An ID given by a professional organization, if any.
An vehicle name given by a professional organization, if any.
The location (longitude) of the vehicle, as specified by the professional organization.
The location (latitude) of the vehicle, as specified by the professional organization.
A description of the vehicle's location.
An ID given by an OEM. -> Deprecated as of API v2.1 in favor of vehicle_identification_number and organization_vehicles.organization_vehicle_id.
The vehicle type as specified by an OEM. -> Deprecated as of API v2.1 in favor of organization_vehicles.organization_vehicle_type_id.
The vehicle's official registration ID. This is usually the license plate number.
The vehicle's official identification number, abbreviated as VIN.
Describes the type of sensor connected to the analog input 1.
NONE, FUEL, BATTERY, BATTERY_2, BATTERY_3, BATTERY_4, 220VLAND, 220VLINV, WATER, WATERINV Describes the type of sensor connected to the analog input 2.
NONE, FUEL, BATTERY, BATTERY_2, BATTERY_3, BATTERY_4, 220VLAND, 220VLINV, WATER, WATERINV Describes the type of sensor connected to the analog input 3.
NONE, FUEL, BATTERY, BATTERY_2, BATTERY_3, BATTERY_4, 220VLAND, 220VLINV, WATER, WATERINV Describes the type of sensor connected to the analog input 4.
NONE, FUEL, BATTERY, BATTERY_2, BATTERY_3, BATTERY_4, 220VLAND, 220VLINV, WATER, WATERINV Description of what is plugged into analog input 1.
Description of what is plugged into analog input 2.
Description of what is plugged into analog input 3.
Description of what is plugged into analog input 4.
Describes the type of sensor connected to the digital input 1.
NONE, 220VLAND, 220VLINV, WATER, WATERINV, ARBTR, ARBTRINV Describes the type of sensor connected to the digital input 2.
NONE, 220VLAND, 220VLINV, WATER, WATERINV, ARBTR, ARBTRINV Describes the type of sensor connected to the digital input 3.
NONE, 220VLAND, 220VLINV, WATER, WATERINV, ARBTR, ARBTRINV Describes the type of sensor connected to the digital input 4.
NONE, 220VLAND, 220VLINV, WATER, WATERINV, ARBTR, ARBTRINV Describes the type of sensor connected to the digital input 5.
NONE, 220VLAND, 220VLINV, WATER, WATERINV, ARBTR, ARBTRINV Description of what is plugged into digital input 1.
Description of what is plugged into digital input 2.
Description of what is plugged into digital input 3.
Description of what is plugged into digital input 4.
Description of what is plugged into digital input 5.
Describes the type of actuator connected to the digital output 1.
NONE, LOCK, NO_REFL, IN_OSZ, IN_ISZ, OSPD_SZ, IN_FRBZ, FUEL_CRT, ARBTR Describes the type of actuator connected to the digital output 2.
NONE, LOCK, NO_REFL, IN_OSZ, IN_ISZ, OSPD_SZ, IN_FRBZ, FUEL_CRT, ARBTR Describes the type of actuator connected to the digital output 3.
NONE, LOCK, NO_REFL, IN_OSZ, IN_ISZ, OSPD_SZ, IN_FRBZ, FUEL_CRT, ARBTR Describes the type of actuator connected to the digital output 4.
NONE, LOCK, NO_REFL, IN_OSZ, IN_ISZ, OSPD_SZ, IN_FRBZ, FUEL_CRT, ARBTR Description of what is plugged into digital output 1.
Description of what is plugged into digital output 2.
Description of what is plugged into digital output 3.
Description of what is plugged into digital output 4.
Describes the number of Bluetooth temperature sensors connected. This can either be NONE
or a string-encoded bit mask of the form XXXX (e.g., 1000 when the first BLE temperature
sensor is connected).
Descriptive text of Bluetooth temperature sensor 1.
Descriptive text of Bluetooth temperature sensor 2.
Descriptive text of Bluetooth temperature sensor 3.
Descriptive text of Bluetooth temperature sensor 4.
Choice of main battery model.
12V-DEF, 24V-DEF, 24V-2x12, 24V-SLB Description of main battery.
Choice of first external battery model.
12V-DEF, 24V-DEF, 24V-2x12, 24V-SLB Description of first external battery.
Choice of second external battery model.
12V-DEF, 24V-DEF, 24V-2x12, 24V-SLB Description of second external battery.
Choice of third external battery model.
12V-DEF, 24V-DEF, 24V-2x12, 24V-SLB Description of third external battery.
Choice of fourth external battery model.
12V-DEF, 24V-DEF, 24V-2x12, 24V-SLB Description of fourth external battery.
The size of the primary tank (in liters).
If an analog tank reading should be preferred over a CAN bus reading (if available).
If the installed IoT device is in hibernation mode (where it sends less data and thus conserves energy).
If the installed IoT device is in transport mode (where trips are recorded, but not saved to the logbook).
If the installed IoT device is in notrack mode (the sensor / location data is not processed).
A subscription to a service within the c.technology cloud ecosystem. This could be for a single vehicle's functionality (most common use case), but also for an additional service such as the vehicle launch service.
Note that you cannot directly create service subscriptions, but have to use another endpoint to do so (Stripe for recurring payments, buy and use a voucher for one-time activations, etc.).
The organizations that are allowed to access this vehicle. The information passed along here might differ depending on your own organizational access.
The configured initial distance before the IoT device was installed.
The configured operation hours before the IoT device was installed.
The data when the IoT device was installed.
If the initialization of this vehicle is complete.
If this vehicle automatically discovers new home locations.
If trips of this vehicle should always stop when it approaches a home location.
If trip points on land should be removed during trip processing.
The type of boat, if applicable.
MOTORBOAT, SAILBOAT The length of the vehicle in meters.
The depth of the vehicle in meters.
The height of the vehicle in meters.
The weight of the vehicle in kilograms.
The vehicle status field that is considered the main battery property.
The vehicle status field that is considered the main fuel property.
Various settings related to how a vehicle is displayed in the native or web app. Currently, this is not editable, but only available as part of a vehicle GET response.