List Notifications
fizzy_get_notificationsFetch account notifications to identify unread items needing attention, including read/unread status, timestamps, and related cards. Page through older read notifications for history.
Instructions
Get notifications for the current user in an account. Returns notification content, read/unread status, timestamps, and related cards or comments. By default (page omitted) returns up to 100 unread notifications followed by the most recent page of already-read ones — this is what you want for 'what needs my attention'. Pages 2 and up contain ONLY older, already-read notifications; no unread notification ever appears there. To walk back through history, call with page=2, then 3, and so on until the array comes back empty. Page size is server-controlled and variable, so never derive counts or remaining history from the length of a page. Use fields='summary' to shrink the embedded card and creator objects down to their key identifying fields — typically several times smaller than the full payload.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page of already-read notification history to fetch (1-based). Omit (or pass 1) for the default response: up to 100 unread notifications followed by the most recent page of read ones. Pages 2 and up contain ONLY older, already-read notifications - no unread ones ever appear there. Page size is server-controlled and variable, so never infer counts or how much history is left from how many items a page returns; walk with page=2, 3, ... until the array comes back empty. | |
| fields | No | Response projection. 'full' (the default — used when this parameter is omitted) returns every field exactly as the API provides it, unchanged from prior behavior. 'summary' strips large, rarely-needed fields — full HTML/rich-text bodies and descriptions, duplicated plain-text/HTML pairs, and repeated embedded objects like the full creator or card — keeping only IDs, names, and short previews. Summary responses are typically 4x to over 100x smaller depending on the tool. Prefer 'summary' when scanning, searching, or listing many results; switch to 'full' (or a single-item fetch tool) once you need complete detail on a specific item. | |
| account_slug | Yes | The account slug identifier (e.g., '123456' or '/123456'). This identifies which Fizzy account to operate on. Get available account slugs from fizzy_get_identity or fizzy_get_accounts. |