Migrate from Public Transit API v3 to Public Transit v8

Note

The missing API versions from v3 to v8 are due to internal version alignment.

HERE offers different versions of the Public Transit API. For guidance on which version best suits your needs, see the Public Transit API v3 Developer Guide.

Preparation

For each (v8) API, the following general actions must be taken to complete the migration:

  • change authentication method (only if you use accessId (v3) credentials parameter)
  • update request parameters
  • update output format

Changes Overview

API

Public Transit API v3 is a single API through which three distinct resources are accessible via dedicated endpoints.

  • .../v3/route
  • .../v3/multiboard
  • .../v3/stations

Public Transit API v8 splits those resources into 3 distinct APIs and modifies request parameters and response output. The APIs and the migration instructions are as follows:

Authentication

We deprecated the accessId parameter (v3), a 20 bytes Base64 URL-safe encoded string used for the authentication of the client application. We changed the way to get credentials with regard to where you access the HERE website. We introduced the OAuth 2.0 Token Credentials authentication method. For more information on the currently available authentication methods, see the Identity & Access Management Guide.

We removed the callbackFunc and callbackId parameters (v3).

Note

The app_code credentials are not supported in v8.

results matching ""

    No results matching ""