I'm a front-end web developer and currently facing a situation where I have one form with few parameters of one object and to save them I should make few requests to few different API endpoints. As I'm used to REST ideology I suppose to have only one API to save one resource.There is some entity, some object with huge number of different properties and to update them I have about 10 different API endpoints for each property groups. This lead to situations where I have one form with few parameters of one object and to save them I should make few requests to few different API endpoints and my nature resists to what seems to me a chaos.As I have talk with my colleagues they explained that this is done due to security reasons - so that some users can access some API endpoints to update some objects properties groups. However I still disagree with situation where I should make few requests to update single object.so here is my questions:I have heard about ACLs but as far as I understand they are to control access to objects, not to individual object's properties. If I'm wrong then how can ACLs' be used in such situation?Why can't be there single API and then server would decide which of properties from request should be updated and which not. So that whole that process would be transparent for me - client side developer?If not ACL then what are the architectures/techniques/approaches should be used in this situation (in web development)
Control access to objects properties
rest;access control