Get the Module Management catalog

OpenAPI contract

Method

GET

Path

/api/v1/processors/modules/catalog

Security

None

Response status

200 400 404 429 500

Request and response schemas

JSON

{
  "requestBody": {},
  "responses": {
    "200": {
      "description": "Module Management catalog",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ModuleCatalogResponse"
        }
      }
    },
    "400": {
      "description": "Invalid request",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/RequestError"
        }
      }
    },
    "404": {
      "description": "Requested processor preset was not found",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ApiError"
        }
      }
    },
    "429": {
      "description": "Rate limit exceeded",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/SecurityError"
        }
      }
    },
    "500": {
      "description": "Unexpected server error",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ApiError"
        }
      }
    }
  }
}

GET /api/v1/processors/modules/catalog is public and returns the versioned Module Management tree. The response describes categories, activation semantics, modes, nested options, dependencies, target-platform selection constraints, defaults, and module scope. Clients should use stable module IDs and wire values instead of inferring configuration from labels or display order.

http

GET /api/v1/processors/modules/catalog