API / FLEETIZE

Preamble

FLEETIZE® is offering you an API to integrate FLEETIZE-rawdata into your 3rd-Party-Application. Our API offers almost all rawdata, used for refined FLEETIZE-Functions.

This API makes it easy to build your own vehicle-fleet-processes. Use it to automate your daily dues according to the states and locations of your vehicles and safe time and reduce your costs. Please mind, that this API only delivers rawdata and does not contain processed or refined results like logbook-route-data eg. Also mind, that this document doesnt represents the full list of all possible API-Commands. In cases you want to do more, please do not hesitate to contact us.

Note: this API-Documentation describes the API starting from FLEETIZE®-Dashboard-Release Version 3.4.49 of 31st January 2021 and all further versions.

Content

Intended Audience
Requirements
Getting your API-Token
Essential Notes for API-Usage
Usage-Limits & Billing
API-Restrictions
Requesting the API
Getting a list of your devices
Getting specific Device- & Route-Information
Tags-Reference

Intended Audience

This documentation is intended for software developers and technical professionals who want to integrate FLEETIZE® rawdata into third-party applications or internal systems.

The FLEETIZE® API is a technical interface designed for system integrations. It allows structured access to vehicle-related data from the FLEETIZE® platform for further processing within custom applications, data pipelines, or analytics tools. This API is explicitly not intended as an end-user reporting interface. Responsibility for correct data interpretation, aggregation, and validation lies with the integrating party.

To successfully use the FLEETIZE® API, we recommend the following knowledge and skills:

Solid understanding of the HTTP protocol
Experience with RESTful web services
Ability to work with JSON-based data structures
Understanding of timestamps, query parameters, data states, and consistency
Experience in building and maintaining technical integrations (e.g. backend services, BI pipelines)

If API data is used for business-critical or billing-relevant purposes, we strongly recommend that the integration is implemented or reviewed by a qualified IT or development team.

Requirements

To use the FLEETIZE® API, the following requirements must be met:

A registered user account at https://login.fleetize.com
At least one active FLEETIZE® device assigned to the account
A valid service plan that explicitly includes API access (API access is a paid feature)

API access is provided on a contractual basis and is subject to the terms of the selected service plan. Depending on the service plan, the scope of accessible data, endpoints, and historical information may vary.

The API token grants technical access to the data of the associated user account. The customer is responsible for ensuring secure handling of the token and for compliance with applicable contractual, legal, and technical requirements.

FLEETIZE® reserves the right to limit, extend, or adjust API access in accordance with the agreed service plan.

Getting your API-Token

To prevent misuse of the FLEETIZE® API, each authorized user must use their own personal API token.

API tokens are available both for the primary account (main user) and for separately created sub-users within a FLEETIZE® account. You can find the API token of each user in the settings menu under "My Account > Administration".

Important differences between API tokens:

Primary Account: The API token of the primary account provides unrestricted access to all data associated with the entire account and all users.
Subuser: API tokens of sub-users can be restricted based on the permissions assigned to the respective sub-user.

For security and access control reasons, we strongly recommend creating a dedicated sub-user specifically for API usage and assigning only the permissions required for the intended integration.

Essential notes for the API-Usage

The FLEETIZE® API exclusively uses Unix timestamps (seconds since 1970-01-01) based on UTC (GMT, see also Wikipedia) without any timezone conversion or daylight saving adjustments. All timestamps provided to or returned by the API are UTC-based. No automatic timezone shifting is applied.

The API differentiates between:

intraday queries (partial time ranges within a day)
full-day queries (from start of day to end of day)

When querying raw or time-based data, the returned result set strictly depends on the specified timestamp range. If a query does not explicitly cover the complete day (e.g. 00:00:00 to 23:59:59 UTC), the returned raw data may differ significantly from full-day or end-of-day results.

It is the responsibility of the integrating application to:

explicitly define start-of-day and end-of-day timestamps when full-day data is required
ensure consistent use of query ranges across API calls
handle timezone conversion and daylight saving time (DST) correctly

Incorrect or incomplete time ranges may lead to apparent data gaps, differences between intraday and end-of-day results, or inconsistencies when comparing API data with exports or reports.

Billing & Usage-Limits

The FLEETIZE® API is a paid feature and is subject to a monthly base fee per vehicle with API access enabled.

API usage is limited on an account level to a total of API requests of (by 6th February 2026):

100 API-Calls per day

This usage quota allows, for example:

an average polling interval of one aggregated request every 15 minutes, or
non-cyclical request patterns with intervals of up to 60 seconds per request

The customer is free to decide how API requests are distributed over time, as long as the defined limits are respected. For most technical integrations, this quota is sufficient when API requests are implemented efficiently and based on a well-designed query logic.

It is the responsibility of the integrating party to ensure that:

API calls are executed with a technically sound request strategy
unnecessary or redundant requests are avoided
the available quota is not consumed by faulty or inefficient implementations

API-Restrictions

Authentication

Each API request must include a valid personal API token. Requests without a token or with an invalid token will result in the following error:

ERROR #1000 - INVALID API TOKEN

Request Rate Limits

Depending on your paid service plan, API requests from the same IP address are limited to one request per 60 seconds. If this limit is exceeded, the following error will be returned and the 60-second counter will be restarted:

ERROR #1055 - QUERY-THRESHOLD EXCEEDED - PLEASE REDUCE QUERY-INTERVAL, OTHERWISE YOUR TOKEN WILL BE BLOCKED

Continuous requests below the allowed interval may result in a temporary block of the API token. In this case, the following error will be returned and you must contact FLEETIZE-support:

ERROR #1002 - QUERY-THRESHOLD EXCEEDED - API TOKEN BLOCKED

Processing Time & Data Volume Limits

API requests are subject to a maximum processing time of 30 seconds per request.

The amount of data that can be retrieved within a single API call depends on the complexity of the request, the queried time range, and the resulting processing time.

It is the responsibility of the integrating application to:

ensure that API requests can be processed within the maximum execution time
limit queried time ranges and data volume accordingly
properly handle timeouts or incomplete responses
implement request throttling, pagination, or batching where required

Requests exceeding the maximum processing time may be aborted or rejected to protect system stability.

IP Address Limitation

Each API request is associated with the calling IP address. Depending on your paid service plan, API access may be restricted to a single IP address at a time.

All API requests are logged. Any misuse, excessive load, or circumvention of rate or processing limits may result in a temporary or permanent suspension of API access.

Requesting the API

Our API can be accessed with simple HTTP-Request REST-Calls, according to the following URI-Structure (Uniform Resource Identifiers):

https://api.fleetize.com/v2/{ActionCode}

Every HTTP-Request has an Action-Code and a different amount of POST-Parameters. Every Action-Request require your personal API-Token. Please mind the API-Restrictions about how to use your personal API-Token correctly.

In all cases requesting the API you will get a JSON-File as a result, containing data of the requested Action-Code.

Getting a list of your devices

Returning all legitimated devices for the given API-Token is possible with the following Action-Request:

https://api.fleetize.com/v2/devicelist

POST-Parameters:

Attribute

Description

apitoken

Your personal API-Token

scope

You can reduce the amount of data by specifying them, eg. "device_id;device_name;"

activity_after

Filter to those vehicles, which had any activity after this unix-timestamp

Filtering the results with scope and activity_after will decrease the amount of data and increase the response time. Especially on a large amount of queryied vehicles, this can prevent to reach api-limitations due to a large amount of data within a period of time.

For scoping the data with scope please provide the needed variable-names separated by semicolons.

The API will respond with all of your legitimated devices including the basic device-data:

[
  {
   "device_id":492,
   "device_imei":359183064907632,
   "device_type":"CAR",
   "device_name":"My vehicle",
   "device_description":"BMW E46 M3 Coupe",
   "device_portrait":"http%3A%2F%2Ftrack.fleetize.com%2Fassets%2Fimg%2Fdevices%2F1471424858072.png",,
   "device_mileage":277910,
   "device_distance":0,
   "online_timestamp":1426576180,
   "heartbeat_timestamp":1426776180,
   "error_code":0,
   "error_text":null,
   "status_absence":"Parking: 1d 10h",
   "status_description":"parked since Di, 17.03., 08:09",
   "status_text":"offline",
   "location":"48.87778,9.34889",
  },
  {
   "device_id":493,
   "device_imei":349133054916622,
   "device_type":"CAR",
   ...
  }
]

Getting specific Device- & Tracking-Information

You can get all device-data and tracking-information by sending the following Action-Request:

https://api.fleetize.com/v2/device

POST-Parameters:

Attribute

Description

apitoken

Your personal API-Token

device

Device-API-ID of the intended vehicle

time

Optional unix-timestamp of targeted day. Leave empty to get data of latest, activity day.

scope

You can reduce the amount of data by specifying them, eg. "device_id;device_name;"

You can find the Vehicle-API-ID within the list of your devices or within the respective vehicle-configuration-page in your FLEETIZE®-Account.

Giving a Timestamp is optionally. If you don't serve a timestamp, the API will export the latest data for the requested device. For Example: for exporting data of the 21st November 2014, please add the Timestamp "1416528000". You also can give the timestamp for 21st November 2014, 11 AM. The API will convert it to 1416528000 so it always returns the vehicle-data of the whole 24 hours of the day.

Scoping the data with "scope" will help you to reduce the transfer data, if you are only interested in partial information. Please provide the needed variable-names separated by semicolons.

In all cases requesting the API you will get a JSON-File as a result, containing all relevant data of the last 24 hours for the given vehicle-id:

{
"device":
  {
   "device_id":492,
   "device_name":"My vehicle",
   "device_description":"BMW E46 M3 Coupe",
   "device_mileage":277910,
   "status_text":"offline",
   "location":"48.87778,9.34889",
  },
"routes":[
  {
   "origin_timestamp":"1428498484",
   "origin_mileage":277843,
   "origin_location":"48.87917,9.19194",
   "destination_timestamp":"1428503164",
   "destination_mileage":277870,
   "destination_location":"48.82556,9.33111",
   "route_points":"48.82556,9.33111,0;48.82556,9.33111,0;...",
  }
]
}

Tags-Reference

Node "device"

Within every API-Request, a JSON-File will be delivered containing the latest vehicle sensor- und location- information in the Parent-Node. The contained Tags are:

Attribute

Description

timestamp

Beginning of output-data, as unix-timestamp

device_id

API-ID of device

device_imei

Device-IMEI

device_type

Type of device

device_name

Name of device, defined by owner

device_description

Description of device, defined by owner

device_mileage

Current FLEETIZE-mileage of device, in kilometers

device_mileage_raw

Current internal mileage of device, in kilometers

device_distance

Day-trip-counter of device, in kilometers

device_portrait

Raw-URL-Encoded path of the image-file

device_speed

Current speed of engine, in km/h

device_upm

Current rounds-per-minute of engine, in r/m

device_temp_engine

Current engine-temperature, in Celsius

device_voltage_external

Current voltage of vehicle-battery, in Volt

device_voltage_internal

Current voltage of device-battery, in Volt

device_angle

Current perspective of device, in degree

online_timestamp

Last Activity-time of device, as unix-timestamp

heartbeat_timestamp

Last Contact to device, as unix-timestamp

error_code

Device-Vault-Code, if present

error_code_time

Time when Device-Vault-Code occured, as unix-timestamp

error_text

device-Vault-Code-description, if present

status_text

Current device-state, as text

status_code

Current device-state, as code

location

Current device-geo-location

Node "routes"

Every tracking-information such as starting and ending time, as well as routepoints are found within this node. The contained Tags are:

Attribute

Description

route_points

Contains all route-points semicolon-seperated: GPS-Latitude,GPS-Longitude,Device-Speed; GPS-Latitude,GPS-Longitude,Device-Speed;â€¦

origin_timestamp

Time while leaving origin, as unix-timestamp

origin_mileage

Mileage while leaving origin, as kilometers

origin_location

Geo-Location while leaving origin

destination_timestamp

Time while reaching destination, as unix-timestamp

destination_mileage

Mileage while reaching destination, as kilometers

destination_location

Geo-Location while reaching destination

average_speed

Average speed of current route while driving (Sum of all speed-packages divided by total packge-amount, null-speed-values are extracted)

average_speed_distance

Average speed of current route while driving (relation between time and distance of the current route)

pause_duration

Duration of all pause in seconds

Node "route_pause"

Within the Node "routes" you will find this node, containing all pause-activities. The contained Tags are:

Attribute

Description

grouped

If there are more than one pause-activities in this area, then value is 1

type

pause-activity-type: 1 = Ignition OFF, 2 = Long-Stopped

start_timestamp

Beginning of pause-activity, as unix-timestamp

end_timestamp

Ending of pause-activity, as unix-timestamp

mileage

Mileage while pause-activity, in kilometers

location

Geo-Location while pause-activity

Attribute "status_code"

Sometimes you will find an attribute called status_code which will define the current state of the specific device:

Code

Description

Offline: Device is parked or in sleeping-mode

Active: Device is active and

Inactive: Device is active but not moving

Not moved yet: Device has no exact status yet

Unused

Attribue "error_code"

There will be Error-Codes delivered within the attribute error_code which will give you more details about what occured:

Code

Description

No Error occured

Modified: Device was plugged-out and plugged-in again

Unplugged: Device is currently unplugged

No Signal: Device is currently not connected

No GPS: Device has no GPS-Signal

Bad GPS: Device has bad GPS-Signal

Need further features?

For special requirements please contact the customecare for more:

Contact

API-Integration

Preamble

Content

Intended Audience

Requirements

Getting your API-Token

Essential notes for the API-Usage

Billing & Usage-Limits

API-Restrictions

Authentication

Request Rate Limits

Processing Time & Data Volume Limits

IP Address Limitation

Requesting the API

Getting a list of your devices

Getting specific Device- & Tracking-Information

Tags-Reference

Node "device"

Node "routes"

Node "route_pause"

Attribute "status_code"

Attribue "error_code"

Need further features?

Die FLEETIZE Fuhrpark-Experten beraten Sie gerne

Anfrage wird verschickt

Bitte haben Sie einen Moment Geduld...

Vielen Dank!