# HTTP integration uplink

**URL:** <https://www.thethingsnetwork.org/forum/t/http-integration-uplink/23478>\
**Category:** Application Development\
**Created:** [March 4, 2019, 11:34am UTC](https://www.thethingsnetwork.org/forum/t/http-integration-uplink/23478 "2019-03-04T11:34:20Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [March 5, 2019, 8:27am UTC](https://www.thethingsnetwork.org/forum/t/http-integration-uplink/23478/7 "2019-03-05T08:27:19Z")

</div>

And like [documented](https://www.thethingsnetwork.org/docs/applications/http/), it’s Base64 encoded:

> ```json
> "payload_raw": "AQIDBA==", // Base64 encoded payload: [0x01, 0x02, 0x03, 0x04]
> "payload_fields": {}, // Object containing the results from the payload functions - left out when empty
> 
> ```

See also [Advantage of Base64 encoding in MQTT?](https://www.thethingsnetwork.org/forum/t/advantage-of-base64-encoding-in-mqtt/3425)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/http-integration-uplink/23478)._