February News from GrahHopper

Previous Article

Ending support for TLS 1.0/1.1

From March 4th, 2020, all requests to the GraphHopper Directions API must use HTTP over TLS (HTTPS), with support for TLS 1.2. We’ve decided to make this change in the best interest of our customers. This way we can ensure the security of data in transit and stay up to date with modern encryption, security protocols, and practices.

This means that TLS 1.0 and 1.1 will no longer be supported for requests to the GraphHopper Directions API. We announced this deprecation for September 2019 and it is finally being implemented.

Update: This update was shifted and done on 22th April.

Releasing the Cluster API

In February, we released our Cluster API. It can be used in many practical applications. For example, it can help to design territories for field workers or to solve large vehicle routing problems. Read our announcement for more information.

New synchronous POST endpoints

The new POST endpoint for the Routing API is useful to handle tens and hundreds of locations without URL restrictions and with the possibility to compress even the request and not just the response.

The new synchronous POST endpoint for the Route Optimization API allows customers to retrieve their solution more quickly and easier without the need of polling queries. Read more in our documentation.

Happy Routing!