# Ticket API Methods Coverage

This document maps every published ticketing endpoint to the current n8n node implementation.
Use it as the single source of truth when adding new ticket capabilities.

## Implemented Operations

| Endpoint | Description | Node Operation | Test Coverage |
| --- | --- | --- | --- |
| `POST /v2/ticketing/ticket` | Create a ticket with full metadata support. | `ticket:create` | `__tests__/ticket.test.ts` → "create operation" case |
| `GET /v2/ticketing/ticket/{ticketId}` | Retrieve ticket details by ID. | `ticket:get` | `__tests__/ticket.test.ts` → "get operation" case |
| `PUT /v2/ticketing/ticket/{ticketId}` | Update ticket metadata (no comments). | `ticket:update` | `__tests__/ticket.test.ts` → "update operation" case |
| `POST /v2/ticketing/ticket/{ticketId}/comment` | Add a comment (supports attachments). | `ticket:comment` | `__tests__/ticket.test.ts` → "comment operation" case |
| `GET /v2/ticketing/tickets` | List tickets with date filtering and pagination. | `ticket:getAll` | `__tests__/ticket.test.ts` → "getAll operation" case |
| `GET /v2/ticketing/trigger/boards` | List available ticketing boards. | `ticket:listBoards` | `__tests__/ticket.test.ts` → "listBoards operation" case |
| `POST /v2/ticketing/trigger/board/{boardId}/run` | Fetch board results with cursor pagination. | `ticket:getTicketsByBoard` | `__tests__/ticket.test.ts` → "getTicketsByBoard operation" case |

Each implemented endpoint is defined in [`nodes/NinjaOne/operations/ticket.ts`](../../nodes/NinjaOne/operations/ticket.ts).

## Pending Coverage Tasks

| Endpoint | Description | Gap Summary | Planned Validation |
| --- | --- | --- | --- |
| `GET /v2/ticketing/ticket/{ticketId}/log-entry` | List ticket log entries. | Not surfaced in the node; requires parameters for pagination/filtering. | Add a dedicated operation and extend `ticket.test.ts` with assertions once implemented. |
| `GET /v2/ticketing/attributes` | Retrieve ticket attributes metadata. | No resource mapping yet. | Add node operation plus schema assertions in a new test block. |
| `GET /v2/ticketing/contact/contacts` | List contact directory entries. | No operation to expose contacts. | Introduce contacts resource with pagination handling tests. |
| `GET /v2/ticketing/ticket-form/{id}` | Retrieve a single ticket form. | Node lacks a ticket form lookup. | Add targeted test verifying routing and required parameters. |
| `GET /v2/ticketing/ticket-form` | List available ticket forms. | Not yet mapped to an operation. | Add test coverage mirroring board listing checks. |
| `GET /v2/ticketing/statuses` | List available ticket statuses. | Missing operation for status reference data. | Add tests validating enumeration mapping. |
| `GET /v2/ticketing/app-user-contact` | Search technician records. | Not currently exposed. | Add tests ensuring query parameters match API expectations. |

Refer back to this table when planning roadmap items so that new work is tied directly to specific endpoints and tests.