Partners and API
An interface for other sites to use railnest data is planned. It does not exist yet — this page describes what is coming and what is not.
What is planned
A read-only interface returning what a station page shows: places to stay and day services within five minutes, with measured walking times, distances, categories and the source of each entry.
It is meant for sites that already send people to trains — booking engines, timetable apps, rail operators, travel magazines. The obvious use is a small box under a connection: eleven places to sleep within five minutes of your arrival station.
Access will need a key, so that we can see how the data is used and tell someone when something changes. There will be a free tier for small volumes.
What it will not be
Not a booking interface. railnest does not take reservations and does not want to stand between a guest and a hotel.
Not a hotel database. We describe the walk from a platform, nothing more. Prices, availability and photographs belong to whoever actually sells the room.
Not a way to buy a better position. The sort order is walking time and stays that way, in the interface as on the site.
Today
There is no public interface yet, no keys are being issued, and there is no waiting list to sign up for.
What already works is linking. Every station has a stable address in the form railnest.net/{language}/station/{station}, in twenty-seven languages, and those addresses do not change — when a station is renamed, the old address redirects permanently. You can link to us today without asking anyone.
If you are interested
Write to us and say what you would want to build. We would rather design the interface around two or three real uses than guess at twenty.
Tell us which countries matter to you, roughly what volume you expect, and whether you need live requests or a nightly file. That is enough to start a conversation.