policyId) and defining the input (input[]) and output (output[]) mappings.key) used in input[] and output[].fields[] must match exactly the keys declared by the Taktile policy at registration time — the engine rejects, at execution time, configuration keys the policy did not declare.policyId, companyId, input[] and output[] at the root level of the payload. Unlike the credit engine configuration, the root-level fields title, description and hasValue are NOT accepted here — sending them returns a 400 error.output[].fields[], the path field is required on create; use the literal value generate when the field's result should be computed automatically by the policy rather than simply passed through.curl --location '/v1/flows//decision-engine-config' \
--header 'Content-Type: application/json' \
--data '{
"companyId": "string",
"policyId": "string",
"input": [
{
"key": "string",
"title": "string",
"type": "string",
"path": "string",
"reference": "string",
"required": true,
"description": "string"
}
],
"output": [
{
"module": "string",
"fields": [
{
"key": "string",
"title": "string",
"description": "string",
"type": "string",
"path": "string"
}
]
}
]
}'{
"id": "string",
"policyId": "string",
"companyId": "string",
"input": [
{}
],
"output": [
{}
]
}