I have a question about the Sesami SDK.
When I execute
await sesami.book(sesamiSlotObject, sesamiCustomerObject, sesamiOptionsObject);
I got a 410 error.
Why am I getting a 410 error?
The data I sent is shown in the attached image.
It would be helpful if you could tell me the cause and solution.
This indicates that the selected slot is no longer available, it can happen for several different reasons.
For example, if a different timezone or team member is used compared to when the availabilities were fetched.
You can start debugging it by inspecting the payload of the request sent to /api/v1/book endpoint, and check if variantId, timezone, team member and all the needed properties are included in the request and are correct.
It could also be a conflicting business logic, for example you might be “reserving” the slot right before “booking” it which can also result in the above error, because by the time you are booking the slot is not available anymore.
Thank you for your response.
I understand now. I had assumed that as long as I specified someone from the Team included in the Service, I would be able to make the booking. Therefore, I was setting a specific team ID for the teamMember, instead of leaving it as null, before proceeding with the booking.
I realize now that this caused the error due to the teamMember being different from the initial one.
Now that I understand the cause, I was able to resolve the issue.
