Bookings REST API no customerId/ customername

Question

We use the Bookings app to reserve workplaces in the office.

If we create an appointment by the reservation form and we make a request off the appointments by the REST API, we will see a customer id equal to null.

--> GET https://graph.microsoft.com/beta/bookingBusinesses/{<!-- -->{id}}/appointments
(https://learn.microsoft.com/en-us/graph/api/bookingbusiness-list-appointments?view=graph-rest-beta&tabs=http)

results:
=> "customerId": null,
"customerName": null,

Can anyone tell me how we can solve this, we need the customerid and name?

Answer 1

@WerkWaterman-0821 It is weird behavior for you. I have created new service using api, then created new appointment using Graph Sample from here and I am able to get customerid. Can you please try executing the above examples. Also, compared your's vs this example if you are passing same attributes.

I this doesn't work I suggest you to please post this on Microsoft Graph support forum to get help from experts.

Answer 2

Hi SaurabhSharma,

The null value is for both, new and existing customers. We created 2 custom services with it's own serviceId.

For now we use the 'Create booking Appointment' with a simple site, outside Office365, but that's not how we planed to do it.

Answer 3

Hi SaurabhSharma-msft,

No problems when i post an appointment by the Graph Explorer, the customerId and customerName is set. This is our current solution.
The problem is when i use the form (see: image).
I will try later to create a new service, maybe we did something wrong by creating the services, i was hoping for a wrong setting.

thanks.

Answer 4

@WerkWaterman-0821 I have tried using the booking page as well with valid and invalid emails but customer id and customer name is getting generated in all scenario's.

What all settings you have selected while publishing the booking URL from bookings page like language, time zone etc. ?

[2]: https://developer.microsoft.com/en-us/graph/support

Answer 5

Hi @SaurabhSharma-msft,

I finally had the time to create a new service and the problem is solved. I don't now what causing the problem by the existing services.

The issue is solved for now.

Thanks