Important note: To help us resolve your issue as quickly as possible, please ensure to fill out all the sections below. Do not share any private information such as email addresses or phone numbers - This is a public Forum!
Briefly describe (1-2 sentences) the Bug you’re experiencing:
Webhook sends sometimes empty events. So the body of the payload from the webhook looks like this:
Steps to reproduce:
We created a webhook like this:
Handshake etc. works fine but some events (always during a certain timespan) arrive with an empty payload (see above).
Hi @Christian_Rickenbach, welcome to the Community Forum
I’m sorry to hear you run into trouble here! I’ve escalated your case to our Development Team so they can investigate further and will get back in touch with you once I hear any updates from them. Thanks!
That’s what a handshake event looks like. How do you know those are not handshake events? (I’m betting they are.)
@Phil_Seeman thanks for your quick answer. Yes you are right, we missed that part in the documentation. We have misinterpreted the term “Empty Payload” in the heartbeat graph and after reading again now the doc properly I found the part that describes this properly:
Note: this list may be empty, as periodically we send a "heartbeat" webhook to verify that the endpoint is still available.
We also found the actual problem that led us to suspect. So everything is working fine for us now.
Thanks for your help
Hi @Christian_Rickenbach, our Development Team has just confirmed that these are heartbeat events. Here’s a link to the API docs for more info.
Webhooks have a “heartbeat” that will deliver an empty payload to your webhook server at the initial handshake, and then every eight hours. This is to ensure the webhook events are still able to be sent to a healthy webhook server.
Happy to hear that everything works fine on your end!
This topic was automatically closed 16 days after the last reply. New replies are no longer allowed.