These things are not what you would see in a headless CMS, and it’s not really how APIs typically function.
I’m not trying to be overly critical and I’m happy v4 is coming along, but… are you telling me the ‘typical’ way to implement user-defined sorting would be to add an extra layer of UI, DB, API proxy etc. between the Frontend and the CMS, just to store and edit order-ids? Please also refer to Ordering Content Type entries in the List view (preferably using drag and drop) · Issue #3946 · strapi/strapi · GitHub