Microsoft Graph Api
4 TopicsBook Appointment - MS Bookings Graph API
Hi, I can create appointments using the MS Bookings API, for particular staff/customers and services in my configured booking business. However I've noticed that the API call does not stop double bookings of staff from being created (same start/end, same staff/service etc). The MS Bookings user interface does seem to detect duplicate bookings (informing the user that they are too late as the staff member is now busy), whether the appointment is occurring at exactly the same points in time, or starts mid-way through an appointment. (I have tested this via multiple browser tabs at the booking page, booking the same appointment in each.) Inspecting the response in the web browser for the bookings UI shows an API response payload with "error": "Status(StatusCode="FailedPrecondition", Detail="Staff not available" Looking at https://learn.microsoft.com/en-us/graph/api/bookingbusiness-post-appointments?view=graph-rest-1.0&tabs=http for the documentation of the API I've noticed that there is very little in regards non-success responses / error codes / oDataError documentation. In fact nothing at all. The only way around this I can see is that on booking an appointment you have to first check availability, but even that seems to be subject to a potential race condition - given that often the API call takes a few seconds to create the appointment and respond with the details. Does anybody know of a better work-around please, or is there some documentation I am missing, seems like a really important part is missing in the book appointment API -namely it should not proceed and should return an appropriate error message/response if the staff member is not available? Or perhaps, this is by design and the app programmer does need to re-check availability ;0 Thanks in advance for any help 🙂974Views0likes2CommentsBooking Appointment Graph API Update No Longer Updates Service Name
The service name property of an appointment was previously editable per docs and testing. https://learn.microsoft.com/en-us/graph/api/bookingappointment-update?view=graph-rest-1.0 Now when an update occurs via API, the service name completely resets to the default service name of the appointments service ID. You can still pass the service name when creating and appointment via the API, but any updates will break it. Anyone else experiencing this issue?227Views0likes0CommentsIs there are way to set an appoinment as "All Day" via the API
The bookings API has come a long way, but it still appears to be missing basic things that are available via the Calendar API. https://learn.microsoft.com/en-us/graph/api/bookingappointment-get?view=graph-rest-1.0&tabs=http Is there a documented (or undocumented) way to get and set the Bookings appointment item as "All Day" from the API? This option exists in the web interface, so it has to be available in the backend somewhere.401Views0likes2CommentsService scheduling policy is not being returned from the API
Hi, We are currently experiencing an issue when making an MS Bookings Graph API call to https://graph.microsoft.com/v1.0/solutions/bookingBusinesses/{BusinessMailbox}/services, the time increments and minimum/maximum lead times are being returned as 0. This applies to all services. For instance, the below service is set to 30 minutes of time increments, 1 hour of minimum lead time and 180 days of maximum lead time. Doing the above API call for this service returns the following response. Is this an issue on the Graph API? "schedulingPolicy": { "timeSlotInterval": "PT0S", "minimumLeadTime": "PT0S", "maximumAdvance": "PT0S", "sendConfirmationsToOwner": false, "allowStaffSelection": false }, Thanks.379Views0likes0Comments