Update decision engine configuration

PUT

/v1/flows/{flowId}/decision-engine-config/{id}

Updates the flow's existing decision engine configuration, fully replacing the submitted input[]/output[].

Unlike creation, this call REJECTS the companyId and hasValue fields at the root level of the payload — sending them returns a 400 error. The path field, required in output[].fields[] on create, must also be omitted here: the behavior is the opposite between create and update.

As with creation, the root-level fields title and description are still not accepted, and the keys in input[]/output[].fields[] must match those declared by the linked Taktile policy (policyId).

Requisição

Parâmetros de Caminho

Parâmetros Bodyapplication/jsonNecessário

Examples

Respostas

🟢200Configuration updated

application/json

The decision engine configuration was updated successfully.

Bodyapplication/json

🟠400Invalid payload

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT '/v1/flows//decision-engine-config/' \
--header 'Content-Type: application/json' \
--data '{
    "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"
                }
            ]
        }
    ]
}'

Response Example

200 - Exemplo 1

{
    "id": "string",
    "policyId": "string",
    "input": [
        {}
    ],
    "output": [
        {}
    ]
}

Modificado em 2026-07-28 20:38:32

Página anterior

Create decision engine configuration

Próxima página

Delete decision engine configuration