Please note that this behaviour is deprecated and may be removed at any time. New integrations should use the information on Specific timetable (desktop) (deprecated, MTT <3.5) and existing integrations should switch over to that format.
To link to a certain timetable directly (the 'module view'), to use the following arguments when linking to
<MyTimetable root URL>/module?:
|Parameter name||Parameter meaning|
|The type of timetable(s) to display. A full list of types can be found in the API documentation at API Documentation#Datastructure. Only 1 type is supported and this type will be used for all specified id's.|
|The unique identifier of the timetable to display. Can be specified multiple times to show multiple timetables, or 0 times when hostKeys are used.|
|The hostKey of the timetable to display. Can be specified multiple times to show multiple timetables, or 0 times when ids are used. Can optionally include one or more 'option host keys' (studentset/pos host keys), by appending them using an exclamation mark as separator.|
|Identifies the database to search. In case of a search on host key this parameter can contain the uniting group key. In case of a search on id this parameter identifies the merging group key. If no value is specified it defaults to a search of all data sources (for host key searches) or the first data source (for id searches).|
Selects the view to display, one of the following values:
|Locale to use, short 2 letter notation (|
|Date to start the calendar at, format |
Chooses the concurrency highlighting option in the list view: (MyTimetable 3.1+)
Host key of the term or named availability to pre-select in the list view (MyTimetable 3.1+).
Prefix with <
- Linking to two locations, by ID: http://mytimetable/module?type=location&id=FDJDF353434&id=FJWO3929AAD
- Linking to a module with selected student set, by hostkey, requiring login and showing the week view: http://mytimetable/module?type=module&hostKey=VAK0001!SS9384&requireLogin=true&view=week