List notifications
Returns a cursor-paginated list of broadcasts in the calling organization, newest first.
Useful for a campaign history dashboard: each item carries current status + stats, so one call renders the whole history with live delivery counters.
See Pagination for the cursor pattern.
Scope: notifications:read.
Authorizations
Your secret API key as a Bearer token: Authorization: Bearer vxn_sk_.... Keys are created and scoped in the dashboard - see Authentication.
Query Parameters
Lifecycle filter - same vocabulary as Notification.status.
queued, scheduled, processing, completed, partial, failed, cancelled Lower bound on created_at - unix seconds or ISO-8601 (inclusive).
Upper bound on created_at - unix seconds or ISO-8601 (inclusive).
1-100. Default 25.
1 <= x <= 100Cursor - the ntf_ id of the last item on the previous page (forward). Numeric offset or page parameters are not supported; cursors are the only supported paging mechanism.
^ntf_[A-Za-z0-9]+$Reverse cursor - returns items before this ntf_ id.
^ntf_[A-Za-z0-9]+$Response
Paginated notification list.
Standard cursor-pagination envelope - see Pagination.
Always "list".
list Array of the requested resource type.
True when more pages exist.
Cursor for the next page in the direction you are already paging, or null when this page ends the collection. has_more: true always comes with a non-null next_cursor.
Feed it back to the SAME parameter you used: starting_after when paging forward (the default), or ending_before when paging backward. Treat it as opaque and do not parse it.
You no longer need to take the last object's id yourself. That still works and is unchanged, but deriving the cursor from the page put the burden of knowing the sort direction on you, and it broke silently on any endpoint whose cursor is not the object id.
"cus_iofv5j4hn6bphinmmyat27tc5y"
Stable collection URL.