Skip to main content
GET
/
notifications
List Notifications
curl --request GET \
  --url https://api.example.com/notifications
{
  "notifications": [
    {
      "id": "<string>",
      "kind": "<string>",
      "payload": "<string>",
      "read_at": "<string>",
      "created_at": "<string>",
      "updated_at": "<string>"
    }
  ],
  "cursor": "<string>"
}

Query Parameters

cursor
string
Cursor for pagination. Use the cursor returned in the previous response to fetch the next page of notifications.

Response

notifications
array
List of notification objects
id
string
Unique identifier for the notification
kind
string
Type of notification (e.g., workflow_completed, job_failed)
payload
string
JSON string containing the notification payload data
read_at
string
ISO 8601 timestamp when the notification was read. Empty if unread.
created_at
string
ISO 8601 timestamp when the notification was created
updated_at
string
ISO 8601 timestamp when the notification was last updated
cursor
string
Cursor for fetching the next page of results. Empty if no more pages available.
The user ID is automatically extracted from the authentication context. Notifications are returned in descending order by creation time.

Example Request

curl -X GET "https://api.chronoverse.com/notifications?cursor=eyJpZCI6MTIzfQ" \
  -H "Authorization: Bearer YOUR_API_TOKEN"

Example Response

{
  "notifications": [
    {
      "id": "notif_12345",
      "kind": "workflow_completed",
      "payload": "{\"workflow_id\":\"wf_abc123\",\"status\":\"success\"}",
      "read_at": "",
      "created_at": "2026-03-03T10:30:00Z",
      "updated_at": "2026-03-03T10:30:00Z"
    },
    {
      "id": "notif_12344",
      "kind": "job_failed",
      "payload": "{\"job_id\":\"job_xyz789\",\"error\":\"timeout\"}",
      "read_at": "2026-03-03T09:45:00Z",
      "created_at": "2026-03-03T09:00:00Z",
      "updated_at": "2026-03-03T09:45:00Z"
    }
  ],
  "cursor": "eyJpZCI6MTIzNDR9"
}

Build docs developers (and LLMs) love