I'm aware this was raised a couple of years back ( #4211 ), happy to comment there if you like but we're having trouble with the decision to not support POST requests here. In our use case, we are specifically sending data to the /route/v1/driving/ endpoint. Many of our routes are 1000+ datapoints, so the URLs become ridiculously long.

We can fix the URL length in clients etc, but many load balancers (which we use to add https and authentication to the service we're running) really dislike URLs that long. For many cloud providers, there simply isn't the option to increase header buffers to that extent and we're forced to roll our own load balancing.

There's also the issue that some of the location data being sent (to map match) are potentially sensitive so access logs containing full routes need to be secured etc.

Would restoring POST support be something you'd consider? Or are we just going to have to live with this?