NinjaOne icon

NinjaOne

Ninja One Public API documentation. <br><br>See also: <br> <a href="https://resources.ninjarmm.com/API/Ninja+RMM+Public+API+v2.0.5+Device+Filter+Syntax.pdf">Device Filter syntax</a><br><a href="https://app.ninjarmm.com/apidocs-beta/core-resources/articles/webhooks/overview">Webhooks</a>

Actions309

Queries → Pending, Failed and Rejected Software patches report

AI-generated

Summary

Retrieve a report listing software patches that are pending, failed, or rejected, optionally filtering and paginating the results.

Inputs

  • Return All — Choose whether to return all results or just a single page of the report.
  • Additional Fields — Optional filters to refine the query, including Device filter (df), Monitoring timestamp filter (ts), Patch Status filter (status), Product Identifier, Patch Type filter (type), Patch Impact filter (impact), Cursor for pagination, and Page Size to limit records per page.
  • Options — Additional options such as custom JSON body overrides, custom HTTP headers, query-string filters, batching controls, debug output, pagination configuration (mode, parameters, limits), and request timeout.

Output shape

a list of software patch records corresponding to pending, failed, or rejected statuses, possibly paginated according to user settings

If 'Return All' is false, the node returns only a single page of results based on pagination settings; otherwise, it fetches all available pages. Debug mode adds details about HTTP requests to the output. Filters and options customize the query request and response handling.

Examples

Example 1: Retrieve all pending, failed, and rejected software patches for a specific device with pagination limiting 100 items per page.

Return All = true; Additional Fields includes df (Device filter) set; Pagination pageSize = 100.

Links

Discussion