API /v1/bookings returns 500 error – "Could not load the sharp module #22176
Replies: 1 comment
-
|
Hi @KaitosAgency! I'm Dosu and I’m helping the cal.com team. This 500 error is caused by a server-side failure to load the "sharp" module, which is used for image processing (like avatars) during booking creation. This isn't related to your payload or environment—it's a backend/deployment issue that affects all booking attempts, even with minimal data. The problem likely stems from a missing or misconfigured dependency on the Cal.com servers, and can't be fixed from your side. There are no recent code changes or documentation addressing this specific error, but similar issues have been resolved by backend fixes in the past (example). The Cal.com team will need to ensure the "sharp" module is correctly installed and available in their runtime environment for bookings to work again. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Cal.com team,
I'm currently facing a blocking issue when trying to create a booking using your API (POST https://api.cal.com/v1/bookings). Every attempt results in a 500 Internal Server Error with the following message:
cpp
Copier
Modifier
Could not load the "sharp" module using the linux-x64 runtime
Possible solutions:
npm install --include=optional sharp
See https://sharp.pixelplumbing.com/install#cross-platform
This issue occurs:
With multiple different eventTypeId values
From different environments (N8N, Postman, your public API playground)
Even with minimal valid payloads
Here’s an example of the body I'm sending:
{
"eventTypeId": 2759308,
"start": "2025-07-07T12:00:00+02:00",
"responses": {
"name": "Valentin Martin",
"email": "v.m***@hotmail.fr",
"location": {
"value": "userPhone",
"optionValue": "06********"
}
},
"timeZone": "Europe/Paris",
"language": "en",
"title": "Valentin Martin à ",
"description": null,
"metadata": {}
}
Can you please investigate this issue urgently? It seems to be affecting all booking creation through the API.
Let me know if you need any additional information. Thanks in advance for your help!
Best regards,
Beta Was this translation helpful? Give feedback.
All reactions