Travelmanager demo
Departure timetable
Show upcoming journeys and help visitors find the next suitable departure.
Only available tours
WORDPRESS INTEGRATION
Add this to your website.
List upcoming departures in chronological order. The following code reproduces the date range and result limit used in this demo.
Add a Shortcode block to your WordPress page and paste the following code.
[travelmanager call="basket" lang="en"]
[travelmanager call="timetable" start="today" stop="3 months" max="12" newwindow="true" lang="en"]Keep the basket shortcode on the same page for journeys that open local trip details. It supplies the booking context and shows the current basket when populated.
Parameters for this example
| Parameter | Value / default | What it does |
|---|---|---|
call | timetable | Use this exact value to select the view shown in this example. |
station_id | All available stations | Optional station ID or comma-separated station IDs. |
linie_id | No route filter | Optional route ID or comma-separated route IDs. Ignored when linie_typ_id is set. |
linie_typ_id | No route-type filter | Optional comma-separated route-type IDs; takes precedence over linie_id. |
start | today | Start date in DD.MM.YYYY or a relative expression such as today or next month. Starts older than one month are reset to today. |
stop | 3 months | Duration measured from start, such as 3 months, without a leading plus. It is not an absolute end date. |
max | 250; demo: 12 | Maximum result count. Use a positive value up to 500; omitted, zero or above 500 falls back to 250. |
newwindow | false | true opens supported booking links in a separate tab/window. |
mandant_id | Empty | Optional numeric tenant filter. |
ressource_id | Empty | Optional numeric resource filter. |
target | Account booking destination | Optional URL of a local details page; generated relation and date parameters are appended. |
godirect | Empty | A nonempty value selects the direct-booking branch for this timetable. This differs from the finder URL parameter. |
view | Visible timetable | ldjson outputs structured event data without a visible timetable. Leave it out for the view shown here. |
Filter a station and route
[travelmanager call="basket" lang="en"]
[travelmanager call="timetable" station_id="2" linie_id="146" start="today" stop="3 months" max="12" newwindow="true" lang="en"]The numeric IDs in the examples are placeholders. Replace them with IDs from your own account. Attribute names and call values stay unchanged in every language.
Account, language and shared options
Install and activate Travelmanager. Save your backend hostname under Settings → Travelmanager and enable Automatic language or select a fixed language. Store the optional private WordPress token there if your account requires it. The examples use the saved account; you can override it with account.
| Parameter | Value / default | What it does |
|---|---|---|
account | Saved setting | Optional backend hostname, for example your-account.travelmanager.software, without https://. Overrides the default account. |
lang | en / de | Language code for this instance, for example en or de. Use Automatic or a fixed language in the plugin settings to enable the current language behavior. |
cache | false | Optional: false bypasses the plugin API-read cache for this call. It does not clear a WordPress page cache or CDN cache. Usually omit this parameter. |
vermittler_id | Empty | Optional numeric referral ID. Existing referral information from a URL or session can also affect the booking context. |
Use literal true and false for boolean attributes. Parameter names such as linie_id, linien_ids and linie_typ_id identify different filters and must not be translated or interchanged.
Try it yourself.
Browse upcoming departures from the English demo account. Open a journey to explore its booking options.