Active Issues API

The Active Issues Management API provides capabilities to monitor and track ongoing issues across your N-able N-central environment. The API allows you to retrieve real-time status information about active issues affecting your managed devices and organization units, enabling proactive monitoring and issue resolution.

API Methods

List Active Issues

Retrieve a comprehensive list of active issues for a specific organization unit. This endpoint is particularly useful for monitoring the health and status of devices within your managed environment.

Key Parameters

orgUnitId: The organization unit identifier (Required)
pageNumber: Page number for paginated results (Optional, defaults to 1)
pageSize: Number of items per page (Optional)
sortBy: Field name to sort results by (Optional)
sortOrder: Sort direction - ASC or DESC (Optional, defaults to ASC)

Response Data Structure

orgUnitId: Organization unit identifier
deviceId: Affected device identifier
notificationState: Current notification status
serviceId: Service identifier
serviceName: Name of the affected service
serviceType: Type of service (e.g., AMP)
taskId: Associated task identifier
serviceItemId: Service item identifier

Extra Information Fields

The API provides additional context through the _extra field, including:

Device name
License mode
Remote control status
Security features status
Backup information
Customer hierarchy details

Key Features

Comprehensive Issue Tracking

Monitor active issues across your entire managed environment with detailed status information for each affected device and service.

Rich Context Data

Access extensive additional information through the _extra field, providing complete context about device status, security features, and management capabilities.

Flexible Pagination

Control result sets with customizable pagination, allowing efficient handling of large data volumes while maintaining performance.

Sorting and Organization

Customize result ordering based on various fields to prioritize and organize issues according to your needs.

Implementation Example

API Request Example

GET /api/org-units/{orgUnitId}/active-issues
Authorization: Bearer <YOUR_ACCESS_TOKEN>

Sample Response

{
  "data": [{
    "orgUnitId": 102,
    "deviceId": 576589254,
    "notificationState": 5,
    "serviceId": 496,
    "serviceName": "Windows UAC Status",
    "serviceType": "AMP",
    "taskId": 2096172314,
    "serviceItemId": 36893,
    "_extra": {
      "deviceName": "NCC-9996",
      "licenseMode": "Professional",
      "remoteControllable": true,
      "customerTree": [
        "System",
        "Service_Organization",
        "Customer 2"
      ]
    }
  }],
  "pageNumber": 1,
  "pageSize": 50,
  "totalItems": 1
}

Notes and Best Practices

Authentication
- All endpoints require a valid API access token
- Include the token in the Authorization header as a Bearer token
Organization Unit Scope
- API currently supports customer and site organization unit types
- Queries must specify a valid organization unit ID
Response Handling
- Implement proper pagination handling for large result sets
- Process the _extra field for complete context about issues
- Handle potential status codes:
  - 200: Successful retrieval
  - 400: Invalid input format
  - 401: Unauthorized
  - 403: Forbidden
  - 404: Resource not found
  - 500: Internal server error