# Webhook URI encoding **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-alerting\ **Created:** [January 15, 2016, 8:36am UTC](https://discuss.elastic.co/t/webhook-uri-encoding/39310 "2016-01-15T08:36:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kuula](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kuula/32/7181_2.png) [@kuula](https://discuss.elastic.co/u/kuula)\ **Post date:** [January 15, 2016, 8:36am UTC](https://discuss.elastic.co/t/webhook-uri-encoding/39310/1 "2016-01-15T08:36:53Z")
I have a pre-encoded URI that I'm trying to call with the Webhook action. ``` /v1/signal/arn%3Aopenstack%3Aheat%3A%3Afcaf9f... ``` Webhook seems to re-encode the %'s in the URI. Resulting in %253A, which doesn't work. The params also have encoded characters if that makes any difference. I tried to put the path in without the encoded characters, tried escaping the %'s with \ and such, but no luck. Any ideas on how to handle this? ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [January 21, 2016, 10:55am UTC](https://discuss.elastic.co/t/webhook-uri-encoding/39310/2 "2016-01-21T10:55:41Z")
Hey, indeed, watcher does an encode of the URI internally, there is no way of changing this behaviour currently, so the easiest solution currently would be to just run another decode as slashes etc should not be touched by that on the client side. --Alex ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:47pm UTC](https://discuss.elastic.co/t/webhook-uri-encoding/39310/3 "2017-07-06T13:47:20Z")