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

.connect resources

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

Documents & Guides

WEBFLEET.connect API documentation
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 analysing driver training needs and providing rewards.


Code examples

WEBFLEET.connect Perl library
A Perl library that wraps around the API. It demonstrates how to interact with WEBFLEET.connect and provides a foundation for other example Perl applications.

WEBFLEET.connect Visual Basic library
Two 'Hello World' examples in Visual Basic illustrating how to retrieve an object list and send a simple text message. One uses the WinHttpRequest 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 demonstrating how to submit requests to WEBFLEET.connect and parse results.


Itinerary waypoint tool
This tool demonstrates how to create itinerary orders in C#. System requirements: .NET 3.5 SP1 or higher.

ASP/VB script 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 applications that enrich data from in-and-around-the-vehicle hardware (barcode scanners, temperature sensors, TPMS, etc.) to the WEBFLEET.connect API.

Documents & Guides

LINK.connect API documentation
Learn how to connect third party devices to the LINK unit via the LINK.connect interface.


Code examples

LINK.connect demonstrator
This Windows PC tool uses the WEBFLEET.connect API to demonstrate the use of LINK.connect. It also connects to a TomTom LINK 410/510 with LINK.connect enabled via Bluetooth. The tool helps you test basic functionality during development of connecting third party hardware via Bluetooth. The tool is written in C#. System requirements: .NET 3.5 SP1, Microsoft Bluetooth stack when using Bluetooth functions.

LINK.connect integration example
This sample project demonstrates 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 functionality on the TomTom PRO 82xx series of ruggedised driver terminals. As a developer, you can customise 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 TomTom LINK device, so your customers need fewer connectivity sources and can save on network costs.

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

SDK


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 SDK documentation
Learn how to use the PRO.connect SDK, including WEBFLEET orders, text messages, custom data and much more.


Code examples

PRO.connect code examples
Learn the basic concepts of the PRO.connect SDK and start developing. Descriptions of the examples are included in the PRO.connect developer guide.

PRO.connect reference implementation
This is a sample code for the standard WEBFLEET order flow and messaging functionality. It allows you to develop a customised 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 TomTom 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 acceleration behaviour, 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 behaviour feedback and road assistance.

SDK

Request API access (API key)


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

  1. Request an API key

    For customers

    If you are a customer and would like to request an API key, complete the online request form. In the Refine search by product model drop-down menu select Integration => Select the API desired. In the Refine search by category drop-down menu select API Request.


    For .connect partners

    If you are a .connect partner, you will receive your API key during your partner application process. To request more API keys, follow the process described above. Click here to go to the online request form.

  2. Set up a dedicated WEBFLEET.connect account
    To complete this step, follow the process described in chapter 3.2.3 of the WEBFLEET.connect API documentation. Alternatively follow the instructions in the video.

Not a .connect Partner yet?