Where can I find more info about the Timetable API (currently in BETA)?

[ana_pino]

Hi, we are creating an integration between our scheduling system and Canvas. 

From what I read in the API there are two ways of creating calendar events:

• The normal one: Using calendar events (POST calendar_events)
• The new one: Using timetables (POST courses/:course_id/calendar_events/timetable) or an event in a time table (POST courses/:course_id/calendar_events/timetable_events).

The problem with the calendar_events is that (as far as I understand) it is not possible to have a sis_id or a foreign id to connect the calendar_event with our system (except having it as a display:none html element hidden in the event description).

timetable_events has a code property that could be used for this. The problem is that: 1) It is in BETA 2) So far it is not possible to retrieve this code using the API and 3) time_table events have no tilte or description making them a bit limited.

The questions are:

• How do I find out if this is an API worth investing time in?
• Does anybody know more about this new API?
• Where can I find more information about its state, possible future and maybe some dates regarding is development? 

The only places I have found any reference to it are the release notes announcing that it is there and the API documentation and a github comment.

[kristinnip]

Hi  @ana_pino ‌

We are currently starting work on our own integration between our scheduling system and Canvas as well.  

I was wondering what path you took, did you go about creating regular calendar events with the SIS_ID added to the event or did you take a closer look at the timetables API?

[ana_pino]

I could not find any other official info about the timetables API except the links listed above so in the end we went with calendar events. It is not perfect but it is working.

[kristinnip]

Thanks Ana.  

That's the route we will likely be going as well.  A more mature timetable event would be nice though

[ana_pino]

Definitely! Good luck with the implementation. 🙂