List notifications
GET /public/v1/notificationsReturns the notifications Sharek has raised for your organization: publishing failures,
channels that need reconnecting, and similar events. This is the API side of the bell in
the app. When one reports a failed post, list posts shows that post
with state set to ERROR.
The CLI has no command for it, and the MCP server has no tool for it.
Query parameters
Section titled “Query parameters”| Parameter | Required | Description |
|---|---|---|
page |
No | Page number, zero-indexed. Defaults to 0. Must be 0 or greater. |
Request
Section titled “Request”First page:
curl -H "Authorization: your-api-key" \ https://dash.sharek.app/api/public/v1/notificationsSecond page:
curl -H "Authorization: your-api-key" \ "https://dash.sharek.app/api/public/v1/notifications?page=1"Response
Section titled “Response”{ "notifications": [ { "id": "notification-id", "content": "Your post to X failed to publish", "link": "https://dash.sharek.app/launches", "createdAt": "2026-09-01T10:00:00.000Z" } ], "total": 143, "page": 0, "limit": 100, "hasMore": true}| Field | Description |
|---|---|
notifications |
The page of results, newest first. |
total |
How many notifications exist in total, not just on this page. |
page |
The page you asked for, echoed back. |
limit |
Always 100. |
hasMore |
true when there are further pages. |
- The page size is fixed at 100 and cannot be changed. There is no
limitparameter; thelimitin the response is informational. - Page beyond the end and you get an empty
notificationsarray withhasMore: false, not an error. - Loop on
hasMorerather than computing pages fromtotal, since new notifications can arrive between requests and shift the offsets. - Reading notifications here does not mark them as read.
- This call is not throttled; only creating posts is (see rate limits).