> For the complete documentation index, see [llms.txt](https://sending-network.gitbook.io/sending.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sending-network.gitbook.io/sending.network/sdk-documentation/push-notifications.md).

# Push Notifications

Sending Network's Push Node works with Push vendors like APNS to enable wallet addresses to receive notifications from peers, dApps, and smart contracts. For example, DEX users can set a desired gas price and be notified when such price is met, saving the efforts of constantly checking back. Or, users from the lending protocol can subscribe to the notifications to be informed when they are about to be liquidated. There are tremendous scenarios where web3 users need to receive these important messages promptly.

Edge nodes send event notifications to the push node configured by the developer. Developers can also configure the edge node to determine which events generate notifications.

A basic flow of push notifications can be sent to Push Providers like Apple’s APNS or Google’s GCM:

1. The client app selects or gets assigned a set of edge nodes.
2. The client app registers with push providers to get a device token.
3. The client app configures the edge node(s) to connect to a Sending.Network Push Node.
4. The edge node sends the notification message to Push Node through HTTP requests with the device token.
5. The Push Node relays the notification message to the push providers like APNS, etc.
6. The Push Provider sends the notifications to the client's device.

<figure><img src="/files/vlokbhrFwCVUUbjsX5D5" alt=""><figcaption><p>Notification Process</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sending-network.gitbook.io/sending.network/sdk-documentation/push-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.