Create a processor preset

OpenAPI contract

Method

POST

Path

/api/v1/processors

Security

jwtBearer (bearer) OR automationKey (bearer)

Response status

201 400 401 403 404 409 429 500

Request and response schemas

JSON

{
  "requestBody": {
    "application/json": {
      "$ref": "#/components/schemas/CreateProcessorRequest"
    }
  },
  "responses": {
    "201": {
      "description": "Processor preset created",
      "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"
        }
      }
    },
    "409": {
      "description": "Request conflicts with current processor state",
      "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"
        }
      }
    }
  }
}

POST /api/v1/processors accepts a JWT or an nfy_ key with processor:write. name is required, nonblank, at most 100 characters, and unique per owner; description is optional (500 characters). steps must be a nonempty list. Each step requires a supported feature ID (maximum 64 characters, letters/digits/underscore/hyphen); optional args is stored after validation but is not parsed into CLI arguments. List order is stored but has no execution-order semantics: resolution joins only nonblank feature IDs.

native-unsafe and native-llvm-direct-call may be included together in steps: they are independent LLVM_CONFIG compiler features. 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

POST /api/v1/processors
Authorization: Bearer <access token>
Content-Type: application/json

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