Partners
Railcation is a metasearch for holiday accommodation you can reach by train. This page is written for affiliate networks and accommodation partners: what the product does, where it stands today, and how an integration with us behaves.
What Railcation is
Railcation searches holiday accommodation and answers the question booking portals leave open: can I actually get there without a car?
Every result carries a realistic door-to-door travel time from the guest's own starting address. That is the rail journey plus the last mile from the arrival station to the front door – on foot, by bus or by taxi, whichever is the sensible way to cover it. Guests filter and sort by that number instead of by straight-line distance to a town centre.
Around the search sit editorial pages: one landing page per destination region, theme pages within a region, and “travelling from city X” pages with pre-computed journey times.
The positioning is car-free travel. Everything on the site is built around the guest who arrives by train.
Market and audience
A German-language product for the German-speaking market (Germany, Austria and Switzerland), with destinations in Germany, Austria and Alsace. The audience is car-free and rail-minded travellers: households without a car, people who avoid flying, and everyone who simply prefers the train to the motorway.
Where we stand
Live. The site is open and indexed. This page alone carries a noindex directive on purpose: it is written for partners, not for guests.
The product runs end to end: search, rail routing, the last-mile calculation, the affiliate hand-off and click tracking are all live and tested.
What is already built
- 33 destination regions, each with its own landing page, grouped by arrival station.
- 159 theme pages – region × theme (hiking, pet-friendly, wellness, winter sports, family, pool & beach, accessible, luxury). A deliberately small first tranche; more combinations are ready and held back until these have been observed.
- 50 “travelling from” pages, one per German departure city, carrying 1,650 pre-computed rail journeys (50 cities × 33 regions).
- 17,000 accommodation records in those regions, from our own curated data set of destinations and properties – each matched to its nearest station with an estimated walking distance. (Raw extract; the pages show slightly fewer, after de-duplication.)
- 20,188 stations and halts across nine countries behind every walking-distance figure.
How an integration with us behaves
This is the part affiliate networks usually want in writing, so here it is in detail.
- Search and hand-off, nothing else. Railcation never takes a booking and never handles a payment. Prices and availability are requested live at the moment a guest searches; the click hands the guest over to the partner's own booking flow, where availability and the final price are confirmed.
- No scraping. Partner data comes from documented APIs only. We do not crawl or scrape partner websites.
- Live prices are not stored. Priced responses sit in an in-process cache for at most ten minutes and are then gone. The single longer-lived entry (60 minutes) is an undated area listing that carries neither prices nor availability. Nothing priced is written to disk or handed on.
- A self-imposed request budget. Outbound partner requests run through our own sliding-window limiter: 100 per minute, a third below what our key is permitted, at most four in flight at a time, everything else queued behind them. A request that cannot get budget within five seconds fails honestly instead of piling up.
- Server-side rate limits. Every publicly reachable endpoint is limited per client IP – between 6 and 60 requests per minute, depending on how expensive the call is; the internal warm-up route is behind a bearer token. The route that resolves a click answers link prefetches with an empty response, so a browser looking ahead never spends a partner request.
- Affiliate links are marked. Every outbound partner link carries
rel="sponsored noopener noreferrer"and opens in a new tab. - Disclosure. The affiliate relationship is disclosed in the footer of every page, in the imprint and in the terms of use.
Our own infrastructure
Timetable routing (MOTIS), walking routes (OSRM) and geocoding (Photon) run on our own servers rather than on public community instances, and the application itself runs on our own hardware as well. The timetable data behind the routing is the German national open GTFS feed; the street and path network is OpenStreetMap.
Two things follow from that for a partner: our traffic never lands on somebody else's free service, and we can keep response times low enough to compute a door-to-door time for a whole page of results rather than for one property at a time.
Data and licensing
The station and accommodation extracts we derive from OpenStreetMap are published under the Open Database License, machine-readable download included, on our data page (German). Prices, photos, descriptions, amenities and guest ratings are never part of that download: those rights sit with the respective partners.
What we are looking for
Accommodation inventory for Germany and the wider German-speaking region, with deep links to a specific property and date range, a workable affiliate programme and reporting we can reconcile. We are happy to run a technical test integration before anyone commits to volume.
Contact
Railcation is operated by Sarah Hirt, sole proprietor, Berlin, Germany.
Full company details are in the imprint (German). Please write in English or German – both are fine.