/filters/versions - Get version filters grouped by product

GET /filters/versions

Get system versions grouped by product type for filtering (requires Support+ role). Returns versions organized by product, suitable for hierarchical UI display.

Version Format: Returns versions in prefixed format product:version (e.g., "nsec:1.2.3", "ns8:1.2.3") to avoid ambiguity when the same version number exists for multiple products.

These prefixed values can be used directly in GET /systems?version= query parameter.

Responses

  • 200 application/json

    Version filters retrieved successfully

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object
      Hide data attribute Show data attribute object
      • versions array[object]

        Versions grouped by product type (each version includes product prefix)

        Hide versions attributes Show versions attributes object
        • product string

          Product type name

        • versions array[string]

          List of versions for this product in prefixed format (product:version)

  • 401 application/json

    Unauthorized - invalid or missing token

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
  • 403 application/json

    Forbidden - insufficient permissions

    Hide response attributes Show response attributes object
    • code integer
    • message string
    • data object | null
GET /filters/versions
curl \
 --request GET 'https://api.your-domain.com/api/filters/versions' \
 --header "Authorization: Bearer $ACCESS_TOKEN"
Response examples (200)
{
  "code": 200,
  "message": "version filters retrieved successfully",
  "data": {
    "versions": [
      {
        "product": "nsec",
        "versions": [
          "nsec:8.6.0",
          "nsec:8.5.2"
        ]
      },
      {
        "product": "ns8",
        "versions": [
          "ns8:1.2.3",
          "ns8:1.1.0"
        ]
      }
    ]
  }
}
Response examples (401)
{
  "code": 401,
  "message": "invalid token",
  "data": {}
}
Response examples (403)
{
  "code": 403,
  "message": "insufficient permissions",
  "data": {}
}