COVID-19 Update.  Find out more

Developer resources

Everything you need to integrate any software and hardware with WEBFLEET and connected vehicle devices.

Webfleet SolutionsWebfleet SolutionsWebfleet SolutionsWebfleet SolutionsWebfleet SolutionsWebfleet Solutions


The WEBFLEET.connect API connects software appli­ca­tions with the WEBFLEET fleet management solution. Via WEBFLEET.connect you can enhance the value of all types of business solutions, including routing and scheduling optimization, ERP, Transport Management System (TMS), supply chain planning, asset management and much more.

Documents & Guides

WEBFLEET.connect API documen­tation
Get started with WEBFLEET.connect. Learn how to send and receive data for the most used WEBFLEET API.

WEBFLEET.connect developer guide – Job dispatch
Send jobs to WEBFLEET and receive job status updates remotely.

WEBFLEET.connect developer guide – Predefined routes over the air
Create predefined routes and include them in your itinerary orders.

WEBFLEET.connect developer guide – Message queues
Using more than one function? Work with message queues. Discover core concepts, tips and tricks.

WEBFLEET.connect developer guide – Driver safety and efficiency
Learn how to use the OptiDrive indicator. Create tools for analyzing driver training needs and providing rewards.

WEBFLEET Plugins developer guide - Integrate your data into WEBFLEET UI
Learn how to display your data in the WEBFLEET user interface.

Code examples

WEBFLEET.connect Perl library
A Perl library that wraps around the API. It demon­strates how to interact with WEBFLEET.connect and provides a foundation for other example Perl appli­ca­tions.

WEBFLEET.connect Visual Basic library
Two 'Hello World' examples in Visual Basic illus­trating how to retrieve an object list and send a simple text message. One uses the WinHttpRe­quest COM object to integrate the WEBFLEET.connect CSV interface; the other one uses the WEBFLEET.connect SOAP interface.

C# example
C# sample projects used in the WEBFLEET.connect developer guide - Driver safety and efficiency.

Delphi example
A basic example in Delphi demon­strating how to submit requests to WEBFLEET.connect and parse results.

Itinerary waypoint tool
This tool demon­strates how to create itinerary orders in C#. System require­ments: .NET 3.5 SP1 or higher.

ASP/VBScript example
A light-hearted ASP page example, showing how to use VBScript to issue requests to WEBFLEET.connect and write the results directly into the page.


LINK.connect is a Bluetooth interface hosted in the LINK tracking device. LINK.connect enables the connection of appli­ca­tions that enrich data from in-and-around-the-ve­hicle hardware (barcode scanners, temperature sensors, TPMS, etc.) to the WEBFLEET.connect API.

Documents & Guides

LINK.connect API documen­tation
Learn how to connect third-party devices to the LINK unit via the LINK.connect interface.

Code examples

LINK.connect demon­strator
This Windows PC tool uses the WEBFLEET.connect API to demonstrate the use of LINK.connect. It also connects to a LINK 510/530 with LINK.connect enabled via Bluetooth. The tool helps you test basic function­ality during development of connecting third-party hardware via Bluetooth. The tool is written in C#. System require­ments: .NET 3.5 SP1, Microsoft Bluetooth stack when using Bluetooth functions.

LINK.connect integration example
This sample project demon­strates the usage of LINK.connect in the case of a driver assignment to a vehicle. Android smartphone on client side and a PHP-based server component are used for this example.


The PRO.connect SDK allows you to access WEBFLEET function­ality on the TomTom PRO 82xx series of ruggedized Driver Terminals. As a developer, you can customize the WEBFLEET order workflow according to your customers’ business needs, including: barcode scanning, digital signature, question paths and photos. Data from the field can be sent to the back office via the LINK device, so your customers need fewer connec­tivity sources and can save on network costs.

The TomTom PRO 82xx series comes with a mobile device management (MDM) system. Our Mobile Device Manager empowers customers to administer their TomTom PRO 82xx series more efficiently. Customers can update and configure devices remotely – and control the content installed on each unit.

Documents & Guides

PRO.connect developer guide
Get started using PRO.connect. Import the PRO.connect SDK into your development environment (Eclipse) and set up a PRO.connect project.

PRO.connect developer guide
Get started using PRO.connect. Import the PRO.connect SDK into your development environment (Eclipse) and set up a PRO.connect project.

Code examples

PRO.connect SDK documen­tation
Learn how to use the PRO.connect SDK, including WEBFLEET orders, text messages, custom data and much more.

PRO.connect reference imple­men­tation
This is a sample of code for the standard WEBFLEET order flow and messaging function­ality. It allows you to develop a customized work order flow for your customers’ team – with minimal effort.


The OBD.connect SDK enables access to vehicle usage and driving performance data through the LINK 100. The LINK 100 is an OBD-II device that plugs into the vehicle’s diagnostic port, connecting the vehicle to a smartphone via Bluetooth. Additionally, customers can view engine performance data in real time and review personal scoring for braking, cornering and accel­er­ation behavior, as well as trips and odometer information. The data can be used to create mobile apps for many purposes, including Usage Based Insurance, leasing, driver behavior feedback and road assistance.


TachoShare.connect is an API that allows partners to access the tachograph data belonging to Webfleet Solutions customers, which is stored in the Webfleet Telematics Service Platform (WTSP). This document provides all the information you need to integrate customer’s tachograph data into your system or application using TachoShare.connect interface.

Documents & Guides

TachoShare.connect API document­ation
Get started with TachoShare.connect. Learn how to get tachograph and driver card files.

Accessing OAuth Webfleet Solutions APIs
Learn how to access to TachoShare.connect API.

Code examples

OAuth client Java example
This sample code shows a Java Spring Web application accessing Webfleet Solutions APIs using OAuth 2.0 author­iz­ation code flow.

Postman collection
The purpose of this collection is to show the different flows involved, starting with the authen­tic­ation and ending with the obtention of tachograph data.

  • Postman collection

    This Postman collection includes three JSON files:

    • production.postman_environment.json defines the URLs of WEBFLEET Authen­tic­ation server and TachoShare.connect.

    • production.postman_environment.json includes all the API calls needed to complete OAuth authen­tic­ation process.

    • TachoShare.connect.postman_collection.json includes all the API calls needed to gather tachograph and driver cards data.

Request API access (API key)

To receive access to the WEBFLEET APIs, please follow the steps below:

  1. Request an API key

    For customers
    If you are a WEBFLEET customer and would like to request an API key (e.g. to connect a 3rd party system with WEBFLEET) please complete our online request form. To access the online request form you need to login to your My Account via the Customer Community on the Webfleet Solutions website or create a new account if required. Then choose API key request in the Category drop-down menu.
    For external integration partners
    If you are a systems integrator and would like to request an API key, please join the .connect Partner Program. Once you are registered in the program, you will receive your first API key. To request further API keys, follow the process described above for customers.
  2. Set up a dedicated WEBFLEET.connect account

    To complete this step, follow the process described in the WEBFLEET.connect API document­ation. Altern­at­ively follow the instruc­tions in the video.

Not a .connect Partner yet?

You are using an outdated browser

Please upgrade to a modern web browser to use this site.

Update now