Automate departureboard.io
HumDay reads departureboard.io’s own published API description and derives 6 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What departureboard.io is
The departureboard.io is a high performance API written in Golang. Its goal is to provide to main functions: (1): A JSON API interface to the legacy National Rail SOAP API: Giving developers the ability to pull live information on departures, arrivals, and services from National Rail, without having to use the legacy SOAP API provided by National Rail. Information is still pulled directly
API host: api.departureboard.io
What HumDay can read from departureboard.io
These are the operations a schedule or a trigger can watch.
- GETgetArrivalsByCRS is used to get a list of services arriving to a UK train station by the CRS (Computer Reservation System) code.
/getArrivalsByCRS/{CRS} - GETgetDeparturesByCRS is used to get a list of services departing from a UK train station by the CRS (Computer Reservation System) code.
/getDeparturesByCRS/{CRS} - GETgetArrivalsAndDeparturesByCRS is used to get a list of services arriving to and departing from a UK train station by the CRS (Computer Reservation System) code.
/getArrivalsAndDeparturesByCRS/{CRS} - GETgetNextDeparturesByCRS is used to get the next service running between two stations.
/getNextDeparturesByCRS/{CRS} - GETgetFastestDeparturesByCRS is used to get the fastest next service running between two stations.
/getFastestDeparturesByCRS/{CRS} - GETgetServiceDetailsByID is used to get information on a service, by the Service ID.
/getServiceDetailsByID/{serviceID}
How automating departureboard.io works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live departureboard.io account.
- Grant access, then go live. You approve the specific departureboard.io operations it may use — and only those.
Automate departureboard.io with these
- ShipEngine84 operations
- eDRV57 operations
- Mercedes Benz Car Configurator24 operations
- Lufthansa LH Partner16 operations
- Wmata Rail Station Information16 operations
- Lufthansa LH Public15 operations
- Wmata Bus Route and Stop Methods12 operations
- Mon voyage pas cher.com Public11 operations
- Deutschebahn Flinkster_API_NG10 operations
- Mercedes Benz Vehicle Image8 operations
- AviationData.Systems Airports6 operations
- Wmata Incidents6 operations
Categories
Questions about departureboard.io automation
- Can HumDay connect to departureboard.io?
- Yes. HumDay reads departureboard.io's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 6 operations are documented.
- Do I need to write code to automate departureboard.io?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your departureboard.io account.
- What can HumDay do in departureboard.io?
- 0 of the 6 documented operations change something in departureboard.io, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my departureboard.io account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to departureboard.io is held behind that approval.
Where this came from
The operations above are read from a published API description for departureboard.io at api.departureboard.io/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2020-11-16.