You are viewing Nextmv legacy docs. ⚡️ Go to latest docs ⚡️



Overview of the available integrations of the Nextmv Cloud API.

There are two types of integrations available for use with Nextmv Cloud: data integrations and platform integrations. These classifications determine which integrations can be included on a single run profile.

  • A data integration extends some functionality used by the Nextmv routing engine. A data integration can be used by a platform integration or by a standard run. Using a data integration can help to enhance results for a particular situation (like using traffic to augment routing input data).
  • A platform integration works with a system that uses route optimization to offer a complete, out-of-the-box solution integrated with Nextmv route optimization. With a platform integration, you would invoke the service through an alternative, integration-specific endpoint.

Multiple integrations can be added to a single run profile. However, there are limitations to the types of integrations that can be combined in a single run profile.

  • A run profile can include up to one platform integration.
  • A run profile can also include up to one data integration for each feature extended (e.g., a run profile can only have one street network integration).

You can use the Nextmv Cloud API with the following integrations:

Onfleetplatformlogistics software for front-end fleet management and dispatching (Onfleet API documentation)
HEREdata (street networks)street network routing API (Documentation for HERE Routing API)
Streetsdata (street networks)Extends Nextmv measures to use real-road networks.

Integrations can be configured via the [Nextmv Cloud Console] console-configuration or API.

Page last updated