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

Billing → Creates an adhoc ticket product.

AI-generated

Summary

Create an adhoc ticket product by specifying required details such as name, description, quantity type, content information, and associations to ticket, product, and account IDs. Include optional settings like tax configuration, user role, and integration settings as needed.

Inputs

  • name (required) — Ticket product name.
  • description (required) — Ticket product description.
  • quantityType (required) — Determines how product quantity is calculated in billing; options include MANUAL, DEVICE_COUNTS, TIME_ENTRIES, END_USER_COUNTS, BACKUP_STORAGE_COUNTS, SOFTWARE_LICENSE.
  • content (required) — JSON object containing product basic information needed for its calculations.
  • ticketId (required) — Ticket ID where the product is assigned.
  • productId (required) — Product ID of the catalog product, if assigned.
  • accountId (required) — Account ID assigned to the product.
  • group (required) — Boolean indicating whether the product can be built as a group.
  • additionalFields — Optional fields such as tax ID, flag to inherit tax from agreement, product user role JSON, and integration settings JSON.
  • options — Optional request customizations including custom body JSON, custom HTTP headers, query filters, batching settings, debug flag, pagination, and timeout.

Output shape

a JSON object representing the created adhoc ticket product.

The output contains the details of the created ticket product including IDs and configured fields. If debug is enabled, request details are included under a debug entry.

Examples

Example 1: Create adhoc ticket product with manual quantity

Specify name, description, quantityType=MANUAL, content JSON, ticketId, productId, accountId, group false, and optionally add taxId and productUserRole in additionalFields.

Links

Discussion