{"id":11069,"date":"2022-07-21T06:23:07","date_gmt":"2022-07-21T13:23:07","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=11069"},"modified":"2022-10-12T16:08:19","modified_gmt":"2022-10-12T23:08:19","slug":"application-permissions-for-bookings-apis-in-microsoft-graph-now-available-on-v1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/application-permissions-for-bookings-apis-in-microsoft-graph-now-available-on-v1\/","title":{"rendered":"Application permissions for Bookings APIs in Microsoft Graph now available on v1"},"content":{"rendered":"

We are delighted to announce that application permissions for Bookings APIs in Microsoft Graph are now available on the v1 endpoint.<\/span>\u00a0<\/span><\/p>\n

Microsoft Graph APIs support both delegated and application permissions on the v1 endpoint. Previously, Bookings APIs in Microsoft Graph supported only delegated permissions. \u202fDelegated permissions require a signed-in user to be present. In the case of Bookings, this meant that only a Bookings calendar administrator, scheduler, team member, or viewer can use APIs. Customers can\u2019t create appointments, which means that custom solutions that support self-scheduling aren\u2019t available. The addition of application permissions unlocks this scenario.<\/span>\u00a0<\/span><\/p>\n

With application permissions, developers can also create bot-like applications and make Bookings part of workflows that don\u2019t need a user to be signed in. Application permissions can also be used to create tools that help tenant admins monitor Booking calendars. Tenant admins can keep track of Booking calendar staff members, publish status and appointment statistics, and more.<\/span>\u00a0<\/span><\/p>\n

APIs with application permissions<\/span><\/b>\u00a0<\/span><\/h2>\n

In this release, we are providing application permissions for a limited set of Bookings APIs. This includes application permissions support for read and write APIs for th<\/span>e \u2018<\/span><\/b>bookingCustomer \u2018<\/span>and \u2018<\/span><\/b>bookingAppointment<\/span>\u2019<\/span><\/b>\u202fentities. For other entities, including<\/span>\u202f\u2018<\/span><\/b>bookingBusiness\u2019,\u202f<\/span>\u2018<\/span><\/b>bookingStaffMember<\/span>\u2019<\/span><\/b>, \u2018bookingCustomQuestion\u2019 and \u2018bookingService\u2019, we are supporting the read APIs only. Because these tasks are for Bookings admins, delegated permissions are recommended for these use cases.<\/span>\u00a0<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
APIs<\/span><\/b>\u00a0<\/span><\/td>\nEntities<\/span><\/b>\u00a0<\/span><\/td>\n<\/tr>\n
Business APIs<\/span><\/i><\/b>\u00a0<\/span><\/td>\n\u00a0<\/span><\/td>\n<\/tr>\n
Get bookingBusiness – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingBusiness<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Service APIs<\/span><\/i><\/b>\u00a0<\/span><\/td>\n\u00a0<\/span><\/td>\n<\/tr>\n
List services – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingService<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Get bookingService – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingService<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Staff Member APIs<\/span><\/i><\/b>\u00a0<\/span><\/td>\n\u00a0<\/span><\/td>\n<\/tr>\n
List staffMembers – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingStaffMember<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Get bookingStaffMember – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingStaffMember<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Appointment APIs<\/span><\/i><\/b>\u00a0<\/span><\/td>\n\u00a0<\/span><\/td>\n<\/tr>\n
List appointments – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingAppointment<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Create bookingAppointment – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingAppointment<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Get bookingAppointment – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingAppointment<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Update bookingAppointment – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingAppointment<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Delete bookingAppointment – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingAppointment<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Customer APIs<\/span><\/i><\/b>\u00a0<\/span><\/td>\n\u00a0<\/span><\/td>\n<\/tr>\n
Get bookingCustomer – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingCustomer<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Update bookingCustomer – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingCustomer<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Delete bookingCustomer – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingCustomer<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Create bookingCustomer – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/a>\u00a0<\/span><\/td>\nbookingCustomer<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
Custom Questions APIs<\/span><\/i><\/b>\u00a0<\/span><\/td>\n\u00a0<\/span><\/td>\n<\/tr>\n
Get bookingCustomQuestion – Microsoft Graph v1.0 | Microsoft Docs<\/span><\/b><\/a>\u00a0<\/span><\/td>\nbookingCustomQuestions<\/span>\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u202f<\/span><\/p>\n

To create appointments using application permissions, you need to use the\u202f<\/span>getStaffAvailability<\/span><\/b>\u202fAPI<\/span><\/a>. At the same time, you should understand how business rules are validated. There is one fundamental difference in creating appointments with delegated permissions as a Bookings admin and creating appointments using application permissions. It is assumed that an admin can override certain business checks as they are aware of their own calendar. However, the same assumption\u00a0<\/span>doesn\u2019t hold while creating appointments using application permissions.<\/span>\u00a0<\/span><\/p>\n

Happy coding!<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

We are delighted to announce that application permissions for Bookings APIs in Microsoft Graph are now available on the v1 endpoint.\u00a0 Microsoft Graph APIs support both delegated and application permissions on the v1 endpoint. Previously, Bookings APIs in Microsoft Graph supported only delegated permissions. \u202fDelegated permissions require a signed-in user to be present. In the […]<\/p>\n","protected":false},"author":69077,"featured_media":6844,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[160,204],"class_list":["post-11069","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph","tag-bookings-api","tag-customer-booking"],"acf":[],"blog_post_summary":"

We are delighted to announce that application permissions for Bookings APIs in Microsoft Graph are now available on the v1 endpoint.\u00a0 Microsoft Graph APIs support both delegated and application permissions on the v1 endpoint. Previously, Bookings APIs in Microsoft Graph supported only delegated permissions. \u202fDelegated permissions require a signed-in user to be present. In the […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/11069","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69077"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=11069"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/11069\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/6844"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=11069"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=11069"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=11069"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}