Code: 200 OK
{"success":false,"message":"Autorisation refus\u00e9e !","total":0,"data":[],"object":[]}This question has been answered by multiple community members. See the first response.
(
)
) in 2.5.1 or 2.5.2 where some actions were assigned a new permission. That was meant to combat a security issue, but had the side effect of requiring a new permission in some cases. That explains why you would not have that problem on an older site with the same permission set (though you really must update that ASAP, the security issues fixed in 2.5.2 are quite severe).