Skip to content
English
  • There are no suggestions because the search field is empty.

🧾 How can I access and use the Fleettracker API V2 endpoints to retrieve ship, bunker (BDN), and log abstract data?

Fleettracker API V2 provides structured access to fleet, bunker delivery notes (BDN), and log abstract (LA) data. To retrieve operational data, users must first obtain ship IDs via the Fleet Overview endpoint and then use these IDs in subsequent API requests. Authentication requires a company GUID and client GUID, which must be requested from your Fleettracker administrator or customer support.

📘 API Overview

Fleettracker API V2 consists of three main endpoints:

  1. Fleet Overview Endpoint → Retrieve ship IDs
  2. BDN Endpoint (Bunker Delivery Notes) → Retrieve bunker data
  3. LA Endpoint (Log Abstract Data) → Retrieve operational report data

All endpoints return data in OVD format *.


🔑 Authentication

All API requests require the following parameters:

  • companyGuid → Identifies your company
  • clientGuid → Identifies your API client

👉 These GUIDs are not generated by users and must be requested from:

  • Your Fleettracker admin, or
  • Fleettracker customer support

🚢 Fleet Overview Endpoint

This endpoint provides a list of all ships in your fleet and their IDs.

URL:

 
https://my.fleettracker.de/api/v2/fleet/
 

Parameters

Parameter Description Data Type Example
companyGuid Company API GUID string 0f0e2f62-2ace-4fc8-b94c-504bf133970e
clientGuid Client API GUID string 6fef1976-52d8-4277-a5dc-080139e4b91f

Returned Data

Field Data Type Description
fleetOverview Array (Ship Objects) Contains all ship objects

Ship Object Structure

Field Data Type Description
id int Ship ID used for further API requests
name string Name of the ship
imoNumber string IMO number of the ship
active bool Indicates if the ship is active in Fleettracker
isBdnBasedReporting bool True if the ship uses BDN-based reporting (DR4)

👉 Important:
The ship ID retrieved here is required for all other API V2 endpoints.


⛽ BDN Endpoint (Bunker Delivery Notes)

This endpoint provides bunker delivery data (BDNs).

URL:

 
https://my.fleettracker.de/api/v2/data/ovd/br
 

Parameters

Parameter Description Data Type Example
companyGuid Company API GUID string 0f0e2f62-2ace-4fc8-b94c-504bf133970e
clientGuid Client API GUID string 6fef1976-52d8-4277-a5dc-080139e4b91f
shipId Ship ID from Fleet Overview int 3251
year Year for which data should be retrieved int 2025

👉 Returns all bunker-related data in OVD format.


📊 LA Endpoint (Log Abstract Data)

This endpoint provides log abstract data (operational reports).

URL:

 
https://my.fleettracker.de/api/v2/data/ovd/la
 

Parameters

Parameter Description Data Type Example
companyGuid Company API GUID string 0f0e2f62-2ace-4fc8-b94c-504bf133970e
clientGuid Client API GUID string 6fef1976-52d8-4277-a5dc-080139e4b91f
shipId Ship ID from Fleet Overview int 3251
year Year for which data should be retrieved int 2025

👉 Returns all log abstract data in OVD format.


🔄 Typical Workflow

  1. Call Fleet Overview Endpoint
  2. Retrieve the ship ID
  3. Use the ship ID in:
    • BDN endpoint → for bunker data
    • LA endpoint → for operational data

⚠️ Notes & Best Practices

  • Access to API endpoints requires proper user permissions
  • Always ensure correct GUIDs are used
  • Data is structured in OVD format for consistency across endpoints
  • The field names used in Fleettracker API V2 responses are aligned with the official DNV OVD Interface Description
  • Use the year parameter to limit data volume and improve performance

* The DNV OVD (Operational Vessel Data) format is an industry-standard data structure used to report operational ship data in a consistent and standardized way.

It was developed by DNV to ensure that data from different ships and systems can be:

  • Easily shared
  • Validated
  • Compared across fleets and stakeholders

In practice, OVD structures data into predefined schemas (tables with fixed fields and rules), mainly:

  • LA (Log Abstract) → Operational events (e.g. departure, arrival, fuel consumption, distance sailed)
  • BR (Bunker Reports) → Fuel bunkering data (BDNs)

This standardized format is widely used for:

  • EU MRV / IMO DCS reporting
  • CII and ETS compliance
  • Data verification and audits

👉 When using Fleettracker API V2, all returned data follows this OVD structure, ensuring compatibility with DNV and other maritime systems.

🔗 Further Reading (DNV / Veracity)