# Receive data using a webhook

**URL:** <https://forums.losant.com/t/receive-data-using-a-webhook/3526>\
**Category:** Help\
**Tags:** workflow, webhook, http\
**Created:** [January 12, 2021, 10:51pm UTC](https://forums.losant.com/t/receive-data-using-a-webhook/3526 "2021-01-12T22:51:57Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Jules\_Huguenin](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/jules_huguenin/32/4031_2.png) [@Jules\_Huguenin](https://forums.losant.com/u/Jules_Huguenin)\
**Post date:** [January 19, 2021, 1:06am UTC](https://forums.losant.com/t/receive-data-using-a-webhook/3526/8 "2021-01-19T01:06:54Z")

</div>

[update]

I have used the experience endpoint as a workaround for my problem with the length of the webhook URL (thanks to [Webhook too long for server](https://forums.losant.com/t/webhook-too-long-for-server/2921)).

The data is coming in nicely in data instead of query, without changing the content-type:  
 ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/d/dbc962b5faeac49f1ea1f58058094aa56052f52d.png)

Do I need to create an Endpoint reply node in my workflow? With or without it I get this response:  
`{ "error": "No endpoint found for this route" }`

Cheers  
Jules

---

_[View the full topic](https://forums.losant.com/t/receive-data-using-a-webhook/3526)._