How to prevent default header parameter from being passed with webhook action in Watcher

adityabk
Wed, 03 Sep 2025 06:12:47 +0000
Elasticsearch

I have a Watcher watch that uses webhook action to send HTTPS request to a Mule API. It looks like this:
</>
”webhook”: {
”scheme”: “XXXX“
”host”: “XXXXX“
”port”: 443
”method”: “post“
”path”: “xxx/yyy/zzz”
”params”: {},
”headers”: {
“client-id”: “XXXXXXXXXXXXX“
“client-secret”: “XXXXXXXXXX“
“Content-Type”: “application/json“
}
”body”: {XXXXXXX}
}
</>

The HTTP response I’m receiving from the Mule API is:
HTTP 403 , invalid header parameter ‘accept-charset‘

I have not set this header in my request. Is this a default header being added? How do I avoid sending it as part of webhook action execution?

4 posts - 2 participants