REST API - PUT - entities : Fieldvalues API - Ignore readonly constraint from restricted field

Context: Inriver allow the user to set a read-only constraint on a field type in two different ways: in the fieldtype details page, or using restricted field. Unfortunately, inriver enforce that in the REST API only from one of those methods ( self promoted article: https://community.inriver.com/hc/en-us/community/posts/8512150805020-REST-API-PUT-entities-Fieldvalues-Readonly-restriction-scope ).

The idea would be to allow the REST API to be constraint less as for the read-only.

Since it is legacy behaviour, you will probably keep that behaviour. So you probably want a "opt-in" kind of feature such as:

• Providing an optional GET parameter

• Providing an HTTP header

• A server setting*

• A new role*

• New API (version)

*PS. Knowing the enrich portal (excluding HTML Template) doesn't even enforce server validation and trust the client, security of an opt-in from the query (client controlled) shouldn't matter.

EDIT: The restriction apply to hidden as well. As for hidden, fetching REST API won't return it either.