This workflow showcases how the Container Input (JSON) and Container Output (JSON) nodes can be used to create a REST API for a workflow that can then be deployed as inference workflow to KNIME Edge. The workflow can be called via REST and classifies a transaction as fraudulent or not fraudulent. In addition to the transaction data, the prediction threshold can be specified in the input.
First, the workflow applies some pre-processing by normalizing the data. Then, it reads in an already trained model and applies it to the input data. A custom prediction threshold is applied with a Rule Engine node to get the final prediction (true for fraud, false for not fraud). Last, the post-processing step brings the output in the correct shape for the response.
When deployed to KNIME Edge, a POST request with the following JSON body can be used for testing:
{
"row-input": {
"V1": -1.65977253845451,
"V2": 1.28590703928839,
"V3": -3.34963337176211,
"V4": 2.05070755935895,
"Amount": 5.49
},
"prediction-threshold": 0.3
}
If setting the prediction threshold to 0.3, the response will be:
{
"Prediction": true
}
If setting the prediction threshold to 0.4, the response will be:
{
"Prediction": false
}
Workflow
Fraud Detection: JSON Input
Used extensions & nodes
Created with KNIME Analytics Platform version 4.4.0
- Go to item
- Go to item
- Go to item
- Go to item
- Go to item
- Go to item
Loading deployments
Loading ad hoc jobs
Legal
By using or downloading the workflow, you agree to our terms and conditions.