_id. The request body is dispatched by the type discriminator, which must match the configured answer type. There is no POST/DELETE: the answer set is fixed by the inspection template.numericValue (send null to clear). Out-of-norm values are accepted (warning is a client concern).textValue (send null to clear).selectedOption.selectedOptionIds (single id unless the answer is multiselect).Authorization: Bearer ********************curl --location --globoff --request PUT 'https://app.hustro.com/api/v2/project//inspection//protocolItem//answer/{{protocolAnswerId}}' \
--header 'hustro-client: web' \
--header 'hustro-client-version: ' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"type": "NUMERIC",
"numericValue": 5
}'{
"_id": "5f479169f7ef7fe33b3cca36",
"checklistAnswerId": "5f479169f7ef7fe33b3cca36",
"type": "COMPLIANCE",
"selectedOption": "PASSED"
}