NinjaOne

Create new organization

List devices for one organization. device_class is sent upstream as df=class=<NodeClass> (the filter GET /v2/devices actually applies; a named nodeClass parameter is ignored) and the page is filtered again so a dropped df cannot return other classes. online is sent as the df online/offline predicate and applied to the page. A full page sets hasMore=true and returns a cursor (the last device id on that page). count is matches in this page, not an organization-wide total.

Get organization details by ID

Get organization custom fields

List organizations (customer accounts)

List organization locations

Update organization custom fields

List scripts and built-in actions available to run on a device, and the credential roles eligible to run as

Run an org-approved script or built-in action on a device (destructive action -- executes code on the customer endpoint). Only scripts the org has pre-approved can run; everything else is refused regardless of this tool's arguments. On HTTP, the caller must already be authenticated (gateway per-request credentials, or a gateway-signed request plus NINJAONE_ALLOW_SERVER_HELD_SCRIPT_EXECUTION for server-held credentials). Confirming the prompt does not authorize the run.

Show API credential status and available tool domains

Add comment to ticket

List ticket attribute (custom field) definitions and their IDs, for the attributes argument of ninjaone_tickets_create and ninjaone_tickets_update.

List available ticket boards for the tenant. Use this to discover board_id values for ninjaone_tickets_list.

Get a ticket's log entries (comments and activity). Pass type to narrow the feed, e.g. type=COMMENT for just the conversation.

List ticketing contacts. Each carries the uid used as a ticket's requester_uid.

Create a new ticket. NinjaOne requires a ticket form, so call ninjaone_tickets_forms_list first and pass its id as ticket_form_id.

Get one ticket form, including its field definitions.

List ticket forms with their fields. Every ticket is created against a form, so use this to find the ticket_form_id for ninjaone_tickets_create.

Get ticket details by ID

List tickets from a ticket board, filterable by status, organization, or device. Requires board_id: NinjaOne queries tickets per board and board IDs vary by tenant (board 1 is NOT always the 'All Tickets' board). Discover board IDs with ninjaone_tickets_boards_list first. NOTE: status/organization/device filters are applied client-side within one board page (NinjaOne's board API cannot filter by them server-side), so the response reports `count` (matches in this page) separately from `scanned`, plus `hasMore`/`cursor` — page through until hasMore is false to get every match; never treat one pa…

List the tenant's configured ticket statuses with their IDs. Statuses are per-tenant, so read them here rather than assuming names like OPEN or CLOSED.

Update an existing ticket's fields. NinjaOne's ticket PUT is a full replace and may reject a partial body — if it does, read the ticket with ninjaone_tickets_get and resend its subject, status, organization_id, ticket_form_id, requester_uid and version alongside your changes. It does not accept comments: use ninjaone_tickets_add_comment for those.

List ticketing users — technicians, end users and contacts. Use this to find the assignee_id (a technician's numeric id) for ninjaone_tickets_create/update.