Update a processor preset

OpenAPI contract

Method

PUT

Path

/api/v1/processors/{id}

Security

jwtBearer (bearer) OR automationKey (bearer)

Response status

200 400 401 403 404 429 500

Request and response schemas

JSON

{
  "requestBody": {
    "application/json": {
      "$ref": "#/components/schemas/UpdateProcessorRequest"
    }
  },
  "responses": {
    "200": {
      "description": "Processor preset updated",
      "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"
        }
      }
    }
  }
}

PUT /api/v1/processors/{id} accepts a JWT or an nfy_ key with processor:write and is owner-only. It is a partial update in implementation: omitted fields remain unchanged, and a non-null steps list replaces all saved steps after feature validation. Step args remains stored metadata only, and list position does not control build execution; only feature IDs are resolved. native-unsafe and native-llvm-direct-call are independent LLVM_CONFIG compiler features and may be stored together. Their combination has been validated with the existing Java 8 workloads, not exhaustively across every JVM, platform, or input; test the exact configuration with representative workloads before release.

http

PUT /api/v1/processors/{id}
Authorization: Bearer <access token>
Content-Type: application/json

{"steps":[{"feature":"native-llvm-direct-call","args":""}]}