Skip to content

List notifications

GET /public/v1/notifications

Returns 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.

Parameter Required Description
page No Page number, zero-indexed. Defaults to 0. Must be 0 or greater.

First page:

Terminal window
curl -H "Authorization: your-api-key" \
https://dash.sharek.app/api/public/v1/notifications

Second page:

Terminal window
curl -H "Authorization: your-api-key" \
"https://dash.sharek.app/api/public/v1/notifications?page=1"
{
"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 limit parameter; the limit in the response is informational.
  • Page beyond the end and you get an empty notifications array with hasMore: false, not an error.
  • Loop on hasMore rather than computing pages from total, 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).