List processor presets

OpenAPI contract

Method: GET
Path: /api/v1/processors
Security: jwtBearer (bearer) OR automationKey (bearer)
Response status: 200 400 401 403 404 429 500

Request and response schemas

JSON

{
  "requestBody": {},
  "responses": {
    "200": {
      "description": "Processor presets",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/ProcessorPresetResponse"
        }
      }
    },
    "400": {
      "description": "Invalid request",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/RequestError"
        }
      }
    },
    "401": {
      "description": "Authentication required or invalid",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/SecurityError"
        }
      }
    },
    "403": {
      "description": "Authenticated but not permitted",
      "content": {
        "application/json": {
          "$ref": "#/components/schemas/SecurityError"
        }
      }
    },
    "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 accepts a JWT or an nfy_ key with processor:read. It returns only presets owned by the caller, newest first. A preset stores an ordered list of steps, but build resolution uses only the nonblank feature IDs from those steps.

http

GET /api/v1/processors
Authorization: Bearer <access token>