> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/service/get-the-callers-unread-notification-count.md).

# Get the caller's unread notification count

Get how many notifications in the caller's own inbox have not been read yet — the number on the bell badge. Counts nothing but the caller's own notifications. This is the endpoint the badge polls, every 30 to 60 seconds. It answers exactly what the notification list with unreadOnly set would return the total count of, without carrying the notifications themselves.

Required permissions: SERVICE\_ORDER

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Service","description":"Service"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"responses":{"ServiceUserNotificationUnreadCountResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceUserNotificationUnreadCountResponseSchema"}}}}},"schemas":{"ServiceUserNotificationUnreadCountResponseSchema":{"title":"ServiceUserNotificationUnreadCountResponseSchema","description":"The number of unread notifications in the caller's own inbox — the number on the bell badge.","type":"object","required":["count"],"properties":{"count":{"type":"integer","description":"How many of the caller's own notifications have not been read yet."}}}}},"paths":{"/tenants/{tenantUid}/serviceorders/usernotifications/unreadcount":{"get":{"summary":"Get the caller's unread notification count","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceUserNotificationUnreadCountResponse"}},"operationId":"get-serviceorders-usernotifications-unreadcount","description":"Get how many notifications in the caller's own inbox have not been read yet — the number on the bell badge. Counts nothing but the caller's own notifications.\nThis is the endpoint the badge polls, every 30 to 60 seconds. It answers exactly what the notification list with unreadOnly set would return the total count of, without carrying the notifications themselves.\n\nRequired permissions: SERVICE_ORDER"}}}}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/developers/api-documentation/service/get-the-callers-unread-notification-count.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
