Integration
Integration with your SIS
A timetabling system that does not talk to your SIS becomes a second source of truth, and second sources of truth diverge. Wise Timetable ships with a documented REST API rather than an integration project.
- Documented REST API
- Inbound and outbound
- Shibboleth SSO
A documented API, in both directions
Inbound so your institutional systems can feed the timetable; outbound so they can read from it.
The REST API allows your student information system, HR system or institutional database to push programme structures, module enrolments, staff records and room inventories into Wise Timetable on a schedule — so the timetable reflects reality without anyone running an export.
In the other direction, your portal, virtual learning environment or in-house mobile app can read timetable data directly for real-time display and automated reporting. That is genuine interoperability rather than a nightly file drop that is stale by lunchtime.
The documentation is a deliverable, not a favour. Your developers should be able to work against the API without a support ticket for every endpoint.
Every integration route
- REST API libraries for inbound and outbound connections
- Scheduled synchronisation with student information and HR systems
- File-based exchange in Excel, CSV and XML where an API is not available
- Direct database integration where institutional policy allows it
- Calendar integration so staff and students can subscribe from Outlook or Google Calendar
- Links to online meeting platforms such as Teams, Zoom and Google Meet attached to individual sessions
Single sign-on
Wise Timetable is compatible with Shibboleth and comparable federated identity systems, which are widely adopted across higher education. Where your institution uses single sign-on, staff and students reach the booking system and their personal timetables with no separate credentials to issue, reset or revoke.
That removes an entire class of administrative overhead, and it removes the security objection that usually accompanies opening a system to several thousand users.
When we have not met your system before
Integration with an unfamiliar external system is the single most common reason an implementation timeline extends. We would rather say that plainly than discover it together in month three.
The integration interface is deliberately flexible and covers most common setups. Tell us which systems you run when you first contact us, and we will tell you honestly whether we have connected to them before and what the effort looks like if we have not.
See Wise Timetable on your own data
Book a 45-minute online presentation. We will walk through your institution's scheduling problem, show how Wise Timetable handles it, and answer anything your team wants to test.