The service accepts a list of locations and generates a map of the most efficient sequence and route for reaching all of them, either in a roundtrip returning to the starting place or one way with first and last stops designated. It helps delivery, transit, or other routing functions to reach required stops as efficiently as possible, avoiding unnecessary backtracking.
API methods accept the route type (roundtrip or one way) and the starting and ending locations, specified as latitude and longitude, along with each of the stops that must be included. The service returns the locations specified listed in the optimal sequence.
The following is a list of historical changes that were made to this asset. Typically, once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change. As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset, we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb. If you spot an error in our data and believe that a record needs to be updated in some way, the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org
22-05-18 14:19:17[Brief] Daily API RoundUp: RouteSavvy, Yapily, CA Veracode, Google Hangouts updated with Related API RouteSavvy SOAP