# Custom Push Notifications: allowed user api push urls

**URL:** <https://meta.discourse.org/t/custom-push-notifications-allowed-user-api-push-urls/54644>\
**Category:** Development\
**Created:** [22 Dicembre 2016, 11:13am UTC](https://meta.discourse.org/t/custom-push-notifications-allowed-user-api-push-urls/54644 "2016-12-22T11:13:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [23 Dicembre 2016, 12:47am UTC](https://meta.discourse.org/t/custom-push-notifications-allowed-user-api-push-urls/54644/3 "2016-12-23T00:47:29Z")

</div>

> [@skoota](#):
>
> does each user who wants to opt-in for push notifications need a user-based API key?

yes

> [@skoota](#):
>
> I am still not sure about the workflow of how a user would start an iOS app, agree to receive push notifications, and then all the stuff on the backend of Discourse happens to allow the push notifications for that user.

When you create your user api key and “approve” the app to read access, push access is implied. This can be controlled by your mobile phone anyway cause you can later on disallow push notifications.

> [@skoota](#):
>
> Is there any information about the format of the request which would be sent to the URL defined in the allowed user api push urls setting, and capabilities required on that server to receive the request?

You are going to have to look at the tests and try it out yourself, totally open to having some public information out there, so go ahead and draft a topic!

---

_[View the full topic](https://meta.discourse.org/t/custom-push-notifications-allowed-user-api-push-urls/54644)._