B12 allows users to synchronize their B12 calendar with their personal Microsoft Outlook or Google Calendar.
To do this, they just need to access their profile from B12, click on the synchronization button of their choice, and follow the instructions.
B12 will then take care of creating, updating, and deleting B12 events to reflect the user's schedules and learning moments planned in B12.
Â
Outlook Calendar
Once access is granted, B12 uses Microsoft Graph API to communicate with a user's calendar. The possible calls are as follows:
-
POST https://graph.microsoft.com/v1.0/me/events
https://learn.microsoft.com/en-us/graph/api/user-post-eventsÂ
-
PATCH https://graph.microsoft.com/v1.0/me/events/:eventId
-
DELETE https://graph.microsoft.com/v1.0/me/events/:eventId
Note that no GET operation is performed. Users' calendars are therefore never read by B12.
An administrator of your tenant will need to authorize the B12 application: https://learn.microsoft.com/en-us/azure/active-directory/develop/application-consent-experience#user-is-directed-to-the-admin-consent-flowÂ
Â
Google Calendar
Once access is granted, B12 uses Google's API to communicate with a user's calendar. The possible calls are as follows:
-
POST https://www.googleapis.com/calendar/v3/calendars/calendarId/events
https://developers.google.com/calendar/api/v3/reference/events/insertÂ
-
PATCH https://www.googleapis.com/calendar/v3/calendars/calendarId/events
https://developers.google.com/calendar/api/v3/reference/events/patchÂ
-
DELETE https://www.googleapis.com/calendar/v3/calendars/calendarId/events
https://developers.google.com/calendar/api/v3/reference/events/delete
Â
Data
- An access_token and a refresh_token (encrypted at rest with AES 256) to perform API calls.
- Opaque reference IDs to update calendar events
Finally, all operations are performed using the HTTPS protocol and encrypted with TLS 1.3.