Network Rail API Platform: Difference between revisions
PeterHicks (talk | contribs) Add NR API platform page |
EvelynSnow (talk | contribs) Aim users directly at the on-wiki downloads page |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Through an API platform hosted by Network Rail, various programmatic interfaces to systems and data are available for consumption. | 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. | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 10: | Line 10: | ||
| [[BPLAN_Geography|BPLAN Geography File]] | | [[BPLAN_Geography|BPLAN Geography File]] | ||
|} | |} | ||
== Suspension of registration == | |||
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, | 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'.