How come this setting causes a 400 bad request when I push the webhook config via the /api/v2/webhooks endpoint? i am trying to route routing.queue.stats events specifically for sla breaches directly into a slack channel using bolt 4. the documentation says i should set the event type to routing.queue.stats and filter on slaBreached but the payload never contains the queue id i need for the slack block kit message. i am hitting the rest api with this body and it keeps rejecting it on validation even though the url is publicly accessible and returns 200 to curl. also the timestamp formatting in the event seems off when it hits my lambda handler. can someone show me the exact json structure for the webhook definition that actually passes validation and includes the queue identifier? i have spent three days debugging this and the error response is completely useless. just need the working payload so i can map it to the slack blocks properly. the notification api bridge keeps dropping events when the filter string is malformed. i tried wrapping the condition in quotes and removing them entirely. nothing works. the server clock in lagos is fine but the event timestamp keeps throwing a parse error in node. please provide the correct schema. i also need to know if the webhook supports batch delivery or if i must handle rate limiting manually on the slack side. every time i deploy the config the platform returns a validation error pointing to the request body template field. i suspect the jsonata expression is invalid but the docs are vague.
{
"name": "sla-breach-slack",
"url": "https://my-lambda-url.execute-api.us-east-1.amazonaws.com/Prod/webhook",
"eventTypes": ["routing.queue.stats"],
"filter": "slaBreached == true",
"enabled": true,
"requestHeaders": {
"content-type": "application/json"
},
"requestBody": {
"template": "{{json}}"
}
}