# Device sending raw data over TagoTiP? Use passthrough + Payload Parser \[Tip #58 Carolina from Support\]

**URL:** <https://community.tago.io/t/device-sending-raw-data-over-tagotip-use-passthrough-payload-parser-tip-58-carolina-from-support/1902>\
**Category:** Support Tips\
**Created:** [June 12, 2026, 7:04pm UTC](https://community.tago.io/t/device-sending-raw-data-over-tagotip-use-passthrough-payload-parser-tip-58-carolina-from-support/1902 "2026-06-12T19:04:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![carolina.hidalgo](https://yyz2.discourse-cdn.com/flex034/user_avatar/community.tago.io/carolina.hidalgo/32/1602_2.png) [@carolina.hidalgo](https://community.tago.io/u/carolina.hidalgo)\
**Post date:** [June 12, 2026, 7:04pm UTC](https://community.tago.io/t/device-sending-raw-data-over-tagotip-use-passthrough-payload-parser-tip-58-carolina-from-support/1902/1 "2026-06-12T19:04:55Z")

</div>

Hey y’all! Carolina from support here!

Had a customer this week ask whether they could send a raw HEX payload over TagoTiP UDP and have the platform automatically convert it to the expected TagoTiP format. Great question! Here we go with the tip, which applies to **all TagoTiP transports** : UDP, TCP, HTTP, and MQTT.

The answer is: Yes! You can totally handle it using raw passthrough + a Payload Parser!

All TagoTiP transports support a raw passthrough prefix ( **\>** ) that lets you send raw bytes directly to your device’s Payload Parser, skipping the standard variable format entirely. The \>x prefix indicates the payload is in HEX format, but other formats are also supported. Just make sure to use the \> prefix so the protocol knows to treat it as raw data.

**UDP:**

echo -n ‘PUSH|4deedd7bab8817ec|sensor-01|\>xDEADBEEF01020304’ \

| nc -u -w1 [udp.tip.us-e1.tago.io](http://udp.tip.us-e1.tago.io) 5683

**TCP:**

echo ‘PUSH|4deedd7bab8817ec|sensor-01|\>xDEADBEEF01020304’ \

| nc [tcp.tip.us-e1.tago.io](http://tcp.tip.us-e1.tago.io) 5693

**HTTP:**

curl -X POST [https://http.tip.us-e1.tago.io/v1/tip/sensor-01](https://http.tip.us-e1.tago.io/v1/tip/sensor-01) \

-H “Authorization: TagoTiP 4deedd7bab8817ec” \

-H “Content-Type: text/plain” \

-d ‘\>xDEADBEEF01020304’

**MQTT:**

mosquitto\_rr -h [mqtt.tip.us-e1.tago.io](http://mqtt.tip.us-e1.tago.io) -p 1883 \

-u 4deedd7b -P ab8817ec \

-t ‘$tip/sensor-01/push’ -e ‘$tip/sensor-01/ack’ \

-m ‘\>xDEADBEEF01020304’

**Note** : \>x is used in the examples above for HEX payloads. Adjust the prefix according to your payload format.

In all cases, the raw bytes are delivered to your device’s **Payload Parser** , where you write a script to decode them and map to TagoIO variables.

So if your device can’t send native TagoTiP format, here are your options:

1. **Best case:** configure the firmware to send native TagoTiP format

2. **Raw passthrough:** use \> and create a Payload Parser to decode the bytes

3. **Device fully locked?** A[middleware](https://docs.tago.io/docs/tagoio/integrations/general/middleware) between your device and TagoIO is the way to go

For the full TagoTiP protocol docs, check out each transport:[UDP](https://docs.tago.io/docs/tagotip/transports/udp) |[TCP](https://docs.tago.io/docs/tagotip/transports/tcp) |[HTTP](https://docs.tago.io/docs/tagotip/transports/http) |[MQTT](https://docs.tago.io/docs/tagotip/transports/mqtt)

Hope this saves someone some time! Let me know in the comments if you have any questions.

Happy Weekend,