Real Time Journey Planner
About
NRE's Real Time Journey Planning (RTJP) service allows users to request journey and fare information from NRE's Online Journey Planner (OJP) service. This API provides the same journey planning functionality as found on the National Rail Enquiries website, including all of the advanced options. It also allows users to have additional options not available via the NRE website, such as the ability to request journeys only (i.e. without fares) or to journey plan for earlier in the day.
Accessing the RTJP API
OJP data feeds are made available under formal licence, requiring signature by both parties. To request a licence, please complete a licence request form and return it to our licensing team at nationalraildatafeeds@raildeliverygroup.com
When licensing the RTJP Webservice to 3rd parties we are obliged to include a licence condition stating that the RTJP Webservice must not be used in conjunction with ticket retailing capability on websites. This condition is imposed by the terms of NRE's usage of a third party service.
OJP Usage Charges
The RTJP Webservice is charged on a transactional basis, with the rate being determined on a cost recovery basis. This means that NRE passes on its costs for usage of a third party journey planning service, without adding any additional charges.
Timetable Groups
The third party journey planning service used by NRE includes the concept of timetable groups. Timetable groups are essentially aliases for multiple locations, allowing a single 'All Stations' group location to be used to submit multiple 'member' locations for journey planning purposes. For example, Coulsdon (All stations) timetable groups can be used to request journeys to/from Coulsdon South OR Coulsdon Town.
It is worth noting that as timetable groups are essentially just a shortcut to specifying multiple locations for journey planning purposes, they are completely independent and unrelated to fare groups (which apply to tickets associated to journeys found after journey planning has occurred). Timetable groups may exist where there is no fare group equivalent (such as the Coulsdon example quoted above) or there may be a timetable group which shares a name with a fare group (e.g. London or Birmingham) but there is no link between them and the may contain different member locations.
| group_id | group_name | group_id | group_name | group_id | group_name | ||
|---|---|---|---|---|---|---|---|