FleetUp API Docs
  1. Account & User & Device
FleetUp API Docs
  • Quick Start
    • Your First API Call
    • Token Expiration
    • Rate Limit
    • Error Codes
  • API Reference
    • Introduction
    • Authentication
      • /token
      • Obtain JWT Token
    • Account & User & Device
      • /account-info
        POST
      • /users
        GET
      • /drivers/list
        GET
      • /devices
        POST
      • /devices/status
        POST
      • /devices/unlock
        POST
      • /devices/driver-overview
        POST
      • /devices/engine-hours
        POST
      • /devices/fuel-level
        POST
      • /devices/odometer
        POST
      • /devices/latest-ecu-data
        POST
      • /devices/{device-id}
        PUT
      • /devices/{device-type}
        GET
      • /devices/{device-type}/details
        POST
      • /devices/{device-type}/history
        POST
    • Trips
      • /trips/history
      • /trips/ongoing-trips
    • Trip Share
      • /tripshare/live-eta
      • /tripshare/partners
      • /tripshare/share
    • Alerts
      • /alerts/summary
      • /alerts/history
      • /alerts/bulk-history
      • /fencealerts/fence-names
      • /fencealerts/geo-fencealerts
    • Location
      • Retrieve GPS data within a 24-hour time range
      • /gpsdata/device-last-location
      • /gpsdata/latest
      • /gpsdata/latest/4cj
      • /gpsdata/latest/5ta
      • /bulk-gpsdata
    • Maintenance
      • /maintenance/history
      • /maintenance/indicators
      • /maintenance/settings/indicators
      • /maintenance/settings/measurements
    • Reports
      • /reports/temperature-sensors
      • /reports/{report-key}
    • Geofence
      • Get all fences
      • Get fence detail
      • Retrieve geofence alerts
    • Others
      • /jobs
  • API Guides
    • Retrieve All Devices from an Enterprise
  • Schemas
    • Schemas
      • DevicesHistoryRequest
      • Devices List Request
      • Geofence Name Response
      • Alerts Bulk History Request
      • Alerts History Request
      • Device List Response
      • Historic Gps Response
      • Device Odometer Response
      • DevicesDetailsRequest
      • DevicesUpdateRequest
      • Get Users Response
      • Ongoing Trips Response
      • Job Creation Response
      • Alerts Summary Response
      • Token Response
      • JWT Token Response
      • Trip History Request
      • DevId with date range Request
      • Device Latest Ecu Data Response
      • Device Data
      • Geofence Alerts Request
      • Latest Gps Request
      • Maintenance History Response
      • Device Status Response
      • Geofence Name Request
      • Historic Gps Request
      • DevId Request
      • Ongoing Trips Request
      • Alerts History Response
      • Account Info Request
      • Device Fuel Level Response
      • Empty Schema
      • Latest 5ta Gps Request
      • DevicesResponse
      • Device List Response
      • Devices Last Location Request
      • Trip History Response
      • DevicesHistoryResponse
      • Geofence Alerts Response
      • Error Schema
      • Device Last Location Response
      • Bulk Historic Gps Request
      • Account Information Response
      • Device Engine Hours Response
      • Devices Status Request
      • Devices Driver Overview Request
      • DevicesDetailsResponse
      • Maintenance Indicators Config Response
      • Latest Gps Response
      • Devices Unlock Request
      • Maintenance Indicators Config Response
      • Drivers List Response
      • Maintenance Indicators Response
      • Job creation request
      • Trip Share Devices Response
      • Live ETA OK Schema
      • TripShare OK Schema
      • TripShare Error Schema
      • Error Schema
      • Temperature Sensor Data Response
      • Geofence List Response
      • Geofence Detail Response
      • Geofence Alert Pagination Response
  1. Account & User & Device

/devices/{device-id}

PUT
/devices/{device-id}
This endpoint allows users to update specific details for either vehicles or assets. Users can update the name and license for vehicles or the license and contents for assets. The request body varies depending on whether the update is for a vehicle or an asset. Only fields related to the selected type should be included. If value of a field is left empty, it will overwrite the existing data with an empty value.

Request

Authorization
Add parameter in header
x-api-key
Example:
x-api-key: ********************
Path Params

Header Params

Body Params application/json

Example
{
    "vehicleName": "string",
    "vehicleLicenseNumber": "string",
    "assetNumber": "string",
    "assetContents": "string"
}

Request Code Samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request PUT '/devices/' \
--header 'token;' \
--header 'x-api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "vehicleName": "string",
    "vehicleLicenseNumber": "string",
    "assetNumber": "string",
    "assetContents": "string"
}'

Responses

🟢200成功
application/json
200 response
Body

Example
{
    "message": "string"
}
Modified at 2025-02-28 08:12:14
Previous
/devices/latest-ecu-data
Next
/devices/{device-type}
Built with