Actions85
- Assessment Actions
- Assessment Data File Actions
- Assessment Data File (Invited) Actions
- Assessment Event Actions
- Assessment Invite Actions
- Assessment Preference Actions
- Assessment Template Actions
- Chatter Actions
- End User Actions
- End User Watchlist Actions
- First Party Alert Actions
- First Party Watchlist Actions
- Leak File Search Actions
- Research Actions
- Third Party Alert Actions
- Third Party Watchlist Actions
Assessment Event → List Events (Page)
AI-generatedSummary
Fetches one page (50 per page) of assessment events from the HackNotice API via POST /assessmentevents/page/:pageNum, optionally filtered by a JSON body.
Inputs
- Page Number — Zero-based page index (default 0, minimum 0). Substituted into the URL path; page size is fixed at 50 by the API. Negative or non-finite values raise an error.
- Request Body — JSON object sent as the POST body, used as a filter/query for events (default {}). Empty, invalid or non-object JSON is silently treated as {}. The accepted filter fields are defined by the HackNotice API and not documented in the node.
- Document ID — Shown in the UI but not used by this operation's path; ignored.
- Invite Code — Shown in the UI but not used by this operation's path; ignored.
Output shape
A list of output items, one per event returned by the API. If the API returns an array, each element becomes an item. A single object becomes one item, and an empty response gives no items. Each item is linked to its input item.
Returns only the requested page, with no automatic pagination. Increment Page Number in a loop to get more. Authentication uses the hackNoticeApi credential. API errors are raised as node API errors.
Examples
Example 1: Retrieve the first page of assessment events
Resource: Assessment Event; Operation: List Events (Page); Page Number: 0; Request Body: {}
Example 2: Fetch the third page of events matching a filter
Page Number: 2; Request Body: JSON filter object such as {"assessment_id":"