Handling Empty Body in message.created / object.created Webhooks

Overview

A message.created webhook with an empty body can occur in instances where the provider creates temporary messages before sending. This notably happens with iCloud. This issue was also present in API V2, where you would have received a webhook and then a 404 error on GET /object.

Please refer to Endpoint 404 Errors: Explanation and Scenarios for more information on why these errors occur.

Handling Procedure

To handle these objects, please apply the following logic, using messages as an example:

1. Receive Webhook: message.created with Empty Body
2. GET /message/{id}
   • If 404 Error Received: Ignore the message.
   • If 200 OK Received: Raise the issue with support.

By following this procedure, you can effectively manage empty body webhooks and minimize unnecessary errors.

Additional Information

For further details, see Endpoint 404 Errors: Explanation and Scenarios

For support, please contact Support Team.

Note: Ensure you have proper logging and monitoring in place to detect and handle these scenarios efficiently.

Updated June 14, 2024 10:16