# Sending Notifications

Apps that want to use our notification protocol will receive access to a notification dashboard from where they can send notifications. They will be able to see several subscribed public keys, their casts, and other general statistics.

Apart from the dashboard, we provide **API** **endpoints** that let apps integrate notifications in their custom business flows. 

Apps can send two types of notifications - **broadcast** and **unicast**. 

* Broadcast notifications are sent to **all** public keys subscribed to the app.
* Unicast notifications are sent to a **single** targeted public key that is subscribed to the dApp.

Broadcast notifications are **not** sent immediately; they are subject to review before being sent to users.

![Creating a cast](/files/3Ud6rfkJHoLnBjdUsPIi)

#### Notification contains

| Field             | Mandatory | Note                        |
| ----------------- | --------- | --------------------------- |
| Title             | Y         |                             |
| Body              | Y         |                             |
| Icon              | Y         | Only shown on web           |
| Image             | N         | Only shown on mobile        |
| Action URL        | N         | Only works on web           |
| Platform          | Y         |                             |
| Cast time         | Y\*       | For broadcast notifications |
| Topic             | Y         |                             |
| Target Public Key | Y\*       | For unicast notifications   |

### Notification Topics <a href="#topics" id="topics"></a>

There are 3 default Notification Topics, users have options to opt-out of specific topics.&#x20;

Currently, we have:&#x20;

**General** - Used for marketing and general announcements&#x20;

**Security** - Used for announcements about security issues&#x20;

**Transactional** - Used when targeting specific/single user(s) about some event/transaction, etc.


---

# Agent Instructions: 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:

```
GET https://docs.solflare.com/solflare/technical/solflare-notifications/sending-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.