Hello,

Thank you for reporting these issues. Here's what I can share regarding the bugs you've encountered:

The API should prevent bookings if the package's capacity is fully utilized. The behavior you're describing, where requests are accepted and result in a "-1" or similar values, indicates a bug in the capacity validation process. We recommend:

• Double-checking the API request payload to ensure it's correctly formatted.
• If the issue persists, please provide more details, including the specific request and response data, to help us reproduce and resolve it.

Appointments created via the API should sync with Google Calendar if the integration is correctly configured. If enrollments are not appearing:

• Verify that the Google Calendar integration is active and properly linked to the employee.
• Ensure the appointments booked through the API are assigned to an employee with an active Google Calendar connection.
• Check the synchronization logs for any errors.

If the issue persists, please provide access to your API logs and Google Calendar settings so we can investigate further.

Thank you for your patience, and we’ll work to resolve these bugs promptly.

Hello Ofek,

Thank you for reaching out!

1. Package Booking Issue: The behavior you observed when no slots are available may relate to mismatched configurations for services or packages. Verify that all necessary details—such as packageCustomer and slot availability—align with your booking logic. Double-check that your request includes valid packageCustomerService attributes. If the issue persists, it could indicate an internal handling inconsistency requiring further review.

2. Google Calendar Integration: To attach bookings to the correct Google Calendar, include the key "googleCalendarEmployeeId": [employee_id] in your request body under the relevant booking object. This ensures the appointment is correctly linked to the employee's calendar.

Let me know if this helps or if you need additional assistance!