Issue Summary

The Cal.com API v2 POST /bookings endpoint returns 500 Internal Server Error, but the booking is still created. Meeting invites and confirmation emails are sent, and the meeting shows in the Cal.com dashboard. The request payload follows the documented format.

Steps to Reproduce

1. Send a POST request to https://api.cal.com/v2/bookings with valid API key and booking payload.
2. Include headers: Authorization: Bearer <api_key>, Content-Type: application/json, cal-api-version: 2024-08-13.
3. Send a payload like:
   {
   "start": "2026-03-03T11:45:00Z",
   "eventTypeId": 3751664,
   "attendee": {
   "name": "Attendee Name",
   "email": "[email protected]",
   "timeZone": "Europe/Berlin"
   }
   }
4. Observe the response.
   Actual Results

• API returns 500 Internal Server Error.
• Response body: {"statusCode":500,"message":"Internal server error"}.
• The booking is created despite the 500: meeting invites and confirmation emails are sent, and the meeting appears in the Cal.com dashboard.
• No additional error details or request ID returned.

Expected Results

• If the booking succeeds: HTTP 200/201 with booking details in the response.
• If it fails: HTTP 4xx with a clear error message.
• A 500 should not be returned when the booking is successfully created.

Technical details

• Cal.com: Cloud (api.cal.com)
• API endpoint: POST https://api.cal.com/v2/bookings
• API version header: cal-api-version: 2024-08-13
• Client: HTTP client from backend application (PHP/Laravel);
• Event type: Using numeric eventTypeId; event type exists and is active in Cal.com

Evidence

• Application logs show 500 responses while meetings are created successfully.