Network Rail API Platform: Difference between revisions

From Open Rail Data Wiki
EvelynSnow (talk | contribs)
Correspondence with Network Rail reveals that new registrations for this API are currently suspended; edit access to past tense, add link to page on PDfeeds reference data, remove optimism about future additions
EvelynSnow (talk | contribs)
Aim users directly at the on-wiki downloads page
 
Line 12: Line 12:


== Suspension of registration ==
== Suspension of registration ==
Network Rail have suspended new registrations, directing data users to access BPLAN via the method described in [[Reference Data]] instead.
Network Rail have suspended new registrations, archived and current BPLAN files can be downloaded from this wiki [[BPLAN Geography Data|here]].


== Requesting access ==
== Requesting access ==


To request access, users would have emailed opendata@networkrail.co.uk.  If granted access, they were given a client ID and client secret.  These were passed in the HTTP message header in the fields 'client_id' and 'client_secret'.
To request access, users would have emailed opendata@networkrail.co.uk.  If granted access, they were given a client ID and client secret.  These were passed in the HTTP message header in the fields 'client_id' and 'client_secret'.

Latest revision as of 10:44, 9 August 2023

Through an API platform hosted by Network Rail, various programmatic interfaces to systems and data are available for consumption. There is currently (June, 2023) only one API, and new registrations are suspended.

API Endpoint Usage
BPLAN (Reference Data) API https://data.networkrail.co.uk/api/pifgeography/v1/train/referenceDataFile BPLAN Geography File

Suspension of registration

Network Rail have suspended new registrations, archived and current BPLAN files can be downloaded from this wiki here.

Requesting access

To request access, users would have emailed opendata@networkrail.co.uk. If granted access, they were given a client ID and client secret. These were passed in the HTTP message header in the fields 'client_id' and 'client_secret'.