Protocol Buffers API
proto.api.traveltimeapp.com/api/v2/
A fast version of time filter communicating using protocol buffers
The request parameters are much more limited and only travel time is returned. In addition, the results are only approximately correct (95% of the results are guaranteed to be within 5% of the routes returned by regular time filter).
This inflexibility comes with a benefit of faster response times (Over 5x faster compared to regular /time-filter endpoint) and larger limits on the amount of destination points.
This endpoint supports doing one to many point searches with following parameters:
- Origin location.
- Destination locations - we recommend a maximum a maximum of 200,000 points per request to ensure optimal performance. When using the Java SDK, it can manage splitting even larger requests into smaller batches.
- Transport mode - possible values are:
PUBLIC_TRANSPORT
,DRIVING+PUBLIC_TRANSPORT
DRIVING_AND_FERRY
,WALKING
, andCYCLING
. - Maximum travel time (in seconds) - only destination locations within this limit will be returned with a travel time. Maximum value is 7200 (2 hours).
- Country - possible values are:
UK
,IRELAND
,FRANCE
,GERMANY
,NETHERLANDS
,AUSTRIA
,BELGIUM
,LITHUANIA
.
All searches are based on a 9am arrival time on a weekday morning.
The responses are in the form of a list where each position denotes either a travel time (in seconds) of a journey, or if negative that the journey from the origin to the destination point is impossible.