# Webhook to specific port **URL:** \ **Category:** The Things Stack v3\ **Created:** [August 6, 2021, 8:20am UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409 "2021-08-06T08:20:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![paul\_tanner](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/paul_tanner/32/38372_2.png) [@paul\_tanner](https://www.thethingsnetwork.org/forum/u/paul_tanner)\ **Post date:** [August 6, 2021, 8:20am UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409/1 "2021-08-06T08:20:39Z")
I am trying to migrate an application to V3. on V2 uplink data was forwarded to a specific port on our development server and processed by an application written in nodejs. So I set up a webhook to http://.org:9090 and enabled uplink data. I see confirmation in the console that forwarding is occurring but do not see the traffic at the receiving end. 2 questions: - is it ok on V3 to forward to a specific port? - what would happen the receiving server blocked it? I ask the second question because, since the application was last used, upgrades on the server may have affected the firewall there. ---
**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\ **Post date:** [August 6, 2021, 9:04am UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409/2 "2021-08-06T09:04:09Z")
> [@paul\_tanner](#): > > is it ok on V3 to forward to a specific port? Yes > [@paul\_tanner](#): > > what would happen the receiving server blocked it? Nothing - web hooks are cute, but there’s no service delivery guarantee - the TTS CE server shouts it out across the internet and does nothing with the response, if any. I find it very reliable as the whole HTTP / Web thing is well developed after decades of use, but the TTS end has no way of knowing if the message was received. ---
**Author:** ![paul\_tanner](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/paul_tanner/32/38372_2.png) [@paul\_tanner](https://www.thethingsnetwork.org/forum/u/paul_tanner)\ **Post date:** [August 6, 2021, 1:40pm UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409/3 "2021-08-06T13:40:34Z")
OK Thanks for that @Nick. I’ve ruled out a firewall issue by posting curl messages from another server:port So I’m stuck for any explanation for the app not seeing any uplink traffic. Is there an example application (pref in nodejs) or an example payload that I can send to help me see what’s happening? Regards. ---
**Author:** ![paul\_tanner](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/paul_tanner/32/38372_2.png) [@paul\_tanner](https://www.thethingsnetwork.org/forum/u/paul_tanner)\ **Post date:** [August 6, 2021, 5:21pm UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409/4 "2021-08-06T17:21:51Z")
OK. I managed to get a dump from TagIO using another webhook. [dump of packet from TagoIO.txt](https://www.thethingsnetwork.org/forum/uploads/short-url/5R76rDWudsmlZB3XkSke9pdg7Sn.txt) (3.1 KB) The format of one uplink packet is so different that my application can’t parse it. So I thought of writing a replacement and looked at the documentation here [Data Formats | The Things Stack for LoRaWAN](https://www.thethingsindustries.com/docs/reference/data-formats/) My attached sample has more in it than the doc shows. It’s also overkill. Is there a handler on V3 that would give us a much simpler JSON message with just timestamp, device id and payload? Regards. ---
**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\ **Post date:** [August 6, 2021, 8:24pm UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409/5 "2021-08-06T20:24:38Z")
> [@paul\_tanner](#): > > My attached sample has more in it than the doc shows. Why would a dump from TagoIO that clearly reformats & adds some extra bits be the same as a web hook direct from TTS? > [@paul\_tanner](#): > > Is there a handler on V3 that would give us a much simpler JSON message with just > timestamp, device id and payload? No This may help: > **[GitHub - descartes/TheThingsStack-Integration-Starters: Starter / Template...](https://github.com/descartes/TheThingsStack-Integration-Starters)** > > Starter / Template code for various The Things Stack (v3) integrations - descartes/TheThingsStack-Integration-Starters ---
**Author:** ![paul\_tanner](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/paul_tanner/32/38372_2.png) [@paul\_tanner](https://www.thethingsnetwork.org/forum/u/paul_tanner)\ **Post date:** [August 7, 2021, 6:45am UTC](https://www.thethingsnetwork.org/forum/t/webhook-to-specific-port/50409/6 "2021-08-07T06:45:34Z")
Yes, that certainly helps. However, I was hoping that V2 to V3 migration would not force a rewrite of our entire nodejs application. I deduce that the V2 integration with nodejs has been deprecated and not replaced. ([https://www.thethingsnetwork.org/docs/applications/nodejs/quick-start/](https://www.thethingsnetwork.org/docs/applications/nodejs/quick-start/) still online) Regards.