Fleet Connectivity Extension API Developer's Guide

Typical Workflow

A typical workflow involving the use of the Fleet Connectivity Extension API consists of the following steps:
  1. The dispatcher sends a POST request with the relevant information about a delivery job. The response from the Fleet Connectivity Extension API service specifies the job ID (job_id) of the job. For an example and more details, see Sending a Job to an Asset.
  2. The dispatcher requests an update on the location and the remaining time till arrival/delivery for each mobile asset that has accepted a delivery job. For an example and more details, see Requesting Updates from the Assets.
  3. After receiving and processing each update, the dispatcher deletes the information from the Fleet Connectivity Extension API service to be ready for the next update. For an example and more details, see Deleting Events.

You cannot use this account to purchase a commercial plan on Developer Portal, as it is already associated to plans with different payment methods.

To purchase a commercial plan on Developer Portal, please register for or sign in with a different HERE Account.

Something took longer than expected.

The project should be available soon under your projects page.

Sorry, our services are not available in this region.

Something seems to have gone wrong. Please try again later.

We've detected that your account is set to Australian Dollars (AUD).
Unfortunately, we do not offer checkouts in AUD anymore.
You can continue using your current plan as normal, but to subscribe to one of our new plans,
please register for a new HERE account or contact us for billing questions on selfservesupport@here.com.