Create card opinion

Registers an analyst's technical opinion for a card on a specific phase. The request body uses three native top-level fields — status, value, and opinion — plus a fields array for the values of the complementary fields configured on the flow.

status is required and accepts approved or rejected. When status is approved, value (the approved value, numeric and greater than or equal to zero) is also required — its absence is rejected. opinion is the analyst's free-text opinion and is optional.

The complementary fields configured on the flow are sent in fields, each item identified by the id returned in the opinion configuration — not by the field name. For select-type fields (select, radio, checkList), the value must be sent as an array, even when only one option is selected.

This endpoint does not accept the limit or comment keys — both are rejected. The card must already be on the phase where the opinion module is enabled before this call; otherwise the action is not available. A second creation call for the same card and phase fails, since the opinion already exists — use the update call to revise it.

curl --location '/v1/cards//phases//actions/opinion' \ --header 'Content-Type: application/json' \ --data '{ "status": "approved", "value": 0, "opinion": "string", "fields": [ { "id": "string", "value": null } ] }'

Create card opinion

Requisição

Respostas