# Sending Notification to Specific User with Onesignal

**URL:** <https://community.thunkable.com/t/sending-notification-to-specific-user-with-onesignal/150022>\
**Category:** Tutorials and DIY Guides\
**Tags:** community, push-notifications, onesignal, webapi, expert, tutorial\
**Created:** [July 21, 2019, 12:58am UTC](https://community.thunkable.com/t/sending-notification-to-specific-user-with-onesignal/150022 "2019-07-21T00:58:23Z")\
**Posts on this page:** 1\
**Showing post:** 61

<div class="post-metadata">

**Author:** ![drted](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/drted/32/92694_2.png) [@drted](https://community.thunkable.com/u/drted)\
**Post date:** [October 25, 2020, 3:49pm UTC](https://community.thunkable.com/t/sending-notification-to-specific-user-with-onesignal/150022/61 "2020-10-25T15:49:18Z")

</div>

Thanks a million to [jacob1](http://community.thunkable.com/u/jacob1) for this great idea!

Like many others, I struggled to get this working. Below is a picture of my “all block” solution to sending a push message ('cuz this is Thunkable, right?)

 ![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/3/e/3e753eb16c96506860c78e8ced05252ca0a20fc2.png)

You will notice that the Headers do not include the Authorization parameter. Interestingly, when using the include\_player\_ids parameter, the API key is not required. One less piece of secure information you do not need to include in your app.

I tried to use the query parameters block, but I kept getting errors so I finally switched to the body block. It is important to note that unlike the query parameters and header blocks, the body block is TEXT not a JSON object, so you need to use the GENERATE JSON FROM OBJECT block to get the body to work correctly.

Happy Thunking!

---

_[View the full topic](https://community.thunkable.com/t/sending-notification-to-specific-user-with-onesignal/150022)._