How to fix 409 conflict issue in MS Bookings API

Hi Sivaranjani Arivazhagan

Thank you for reaching out via the Microsoft Q&A forum.

To help isolate the issue, could you kindly confirm whether this error occurs when attempting to add a completely new user who has never existed in the system before?

Based on my research, it appears the issue is specific to scenarios involving the re-addition of previously deleted users. This stems from a fundamental difference in how the user portal and the underlying API handle user deletion.

• API Behavior: The API’s POST command is strictly intended for creating new resources. If it detects that a user already exists, whether active or recently deleted, it returns a 409 Conflict error. This is expected behavior, as the API cannot create a duplicate record.
• Portal Behavior: The web portal is designed to be more user-friendly. It first checks for existing users and, if found, links the existing account to the Bookings business rather than attempting to create a new one. This is why the action succeeds in the portal.

In summary, the portal may be attempting to "reactivate" the user, while the API is trying to "create new," which fails because the user is not truly new from the database’s perspective.

Additionally, you may find that there are other threads reporting the same error code in situations similar to the one I’ve described.

• I deleted a staff member from my bookings page. - Microsoft Q&A
• Deleting staff from Microsoft Bookings | Microsoft Community Hub

I hope this clarifies the situation for you. Please let us know if you have any further questions.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hi,

Thank you for your response.

To answer your question:

Approach 1: Yes, the user exists in Azure AD. I'm using the user's email and display name to create the staff member for the business via the API.

• Approach 2: I also tried using a completely new user who does not exist in Azure AD, but I still received the same 409 error.

Could you please guide me on the correct way to add staff members using the API?

Thanks,
Siva