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

Elastic Stack Elasticsearch
,
1

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?

2

It looks like that header is set here, and that there is no way to avoid it unfortunately. Is there no way to configure the Mule API to ignore it (I am not familiar with that API at all)?