policyId) and defining the input (input[]) and output (output[]) mappings.title (string), description (string) and hasValue (boolean) at the root level of the payload, both on create and on update — missing any of them returns a 400 error.key) used in input[] and output[].segments[].fields[] must match exactly the keys declared by the Taktile policy at registration time. The native fields score, rating and value are computed automatically by the engine at runtime and must NOT be included in output[].segments[].fields[] — only the criteria defined by the policy.output[].segments[].fields[] do not have a path — only aggregates[] items, when present, have a path, pointing to the source of each aggregated value.curl --location '/v1/flows//credit-engine-config' \
--header 'Content-Type: application/json' \
--data '{
"companyId": "string",
"title": "string",
"description": "string",
"hasValue": true,
"policyId": "string",
"input": [
{
"key": "string",
"title": "string",
"type": "string",
"path": "string",
"reference": "string",
"required": true,
"description": "string"
}
],
"output": [
{
"description": "string",
"segments": [
{
"description": "string",
"fields": [
{
"key": "string",
"title": "string",
"description": "string",
"type": "string",
"weight": 0,
"aggregates": [
{
"key": "string",
"path": "string",
"description": "string"
}
]
}
]
}
]
}
]
}'{
"id": "string",
"policyId": "string",
"companyId": "string",
"title": "string",
"description": "string",
"hasValue": true,
"input": [
{}
],
"output": [
{}
]
}