[CAL-3004] "Seats Per Time Slot" property not being respected

[jdiogomagalhaes]

Issue Summary

When testing the event type's seatsPerTimeSlot property, we've come across an issue. The property was set to 4, yet only 2 clients could book the same time slot. So we've tested it with 5, and now 3 clients could book... we've tested it with 6, still only 3 clients could book. And finally, with the seatsPerTimeSlot property set to 7, we've managed to limit the time slots as expected.

Problem 1: Why did I need to set the property to 7?
Problem 2: When creating bookings via API, this property is not taken into consideration at all. It doesn't merge client events in the Cal.com user's google calendar, as it happens with the embed scheduler, and it also allows me to create as many bookings as I'd like (even if I use the same email more than once, the booking is still created). Why is that?
Final Question (perhaps not a problem): Why's there a seatsPerTimeSlot at the booking level? I've tried setting this property to 4 on the event type and also on the booking, but still no limits are being applied. That's already defined on the event type

Steps to Reproduce

1. Create event type with 4 seats
2. Create booking of this event type via API
3. Try getting the API to forbid the creation of the booking based on the seatsPerTimeSlot (I couldn't)

Technical details

• Using postman to create bookings:
  {
  "metadata": {},
  "eventTypeId": 541371,
  "start": "2024-01-30T11:00:00.000Z",
  "end": "2024-01-30T12:00:00.000Z",
  "seatsPerTimeSlot": 4,
  "responses": {
  "name": "Hello Hello",
  "email": "jose.magalhaes@papayya.com",
  "location": "Papayya HQ"
  },
  "timeZone": "Europe/Lisbon",
  "language": "en",
  "title": "Debugging between Jose and Hello Hello",
  "description": null,
  "status": "ACCEPTED"
  }

Evidence

_{From SyncLinear.com | CAL-3004}

[MehulZR]

Is this related to enterprise API?

[jordankrueger]

I believe I've also come across this same problem – we have a Team with an Event Type that allows 3 meetings per day and 10 seats per meeting. When the limit on meetings was reached, the day was blocked off on the availability calendar even though seats were still available for each of the events.

I've worked around this by lifting the number of meetings available per day, adding an additional team member account and blocking off their calendar on all the days we're available for the next few weeks. That way, Cal.com won't allow a new booking on any of those days, but it still shows all the available bookings that still have slots.