Updates the vehicle fields you send; fields you leave out keep their value. PATCH works the same way. The class, location (use relocations), make and model, and telematics device cannot be set here.Permissions. The API user needs the permission to update vehicles, plus the permission to change the status, the odometer or the fuel level when you send status, odometer or fuel_level. Without it the answer is a real HTTP 403.Status. A vehicle cannot be set to rental here (reservations do that), and a vehicle that is on a rental cannot be moved to another status. Changing the status fires the fleets_vehicle_status_changed webhook. Moving a vehicle to on_sale, sold, stolen, recovered, totaled or repossessed removes it from all open reservations (they are re-assigned to another vehicle only when availability per location is enabled). For on_sale and sold, the telematics device is also unlinked unless the account turns that off in its Fleets settings.VIN. The VIN must be unique. Leave vin out when it does not change.Custom fields are sent as field_<id>; custom fields you do not send keep their value.
The updated vehicle in data.vehicle. HTTP 200 is also used for failures: always check success. When it is false, the body is an ErrorBusinessRule (status_code 410) or an ErrorUnauthorized (status_code 401 or 403).