# Storage partial update by REST API **URL:** \ **Category:** Game Design\ **Created:** [January 17, 2020, 4:22pm UTC](https://forum.heroiclabs.com/t/storage-partial-update-by-rest-api/466 "2020-01-17T16:22:12Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![novabyte](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/novabyte/32/1324_2.png) [@novabyte](https://forum.heroiclabs.com/u/novabyte)\ **Post date:** [January 19, 2020, 10:26pm UTC](https://forum.heroiclabs.com/t/storage-partial-update-by-rest-api/466/2 "2020-01-19T22:26:13Z")
@nkadd I wrote a large post on how best to do this at the moment with Nakama server: > [@Query by JSON data & Indexing](https://forum.heroiclabs.com/t/query-by-json-data-indexing/362/2): > > Hey @Ndidi. This is a great post. Thanks for the question. I’ll share as much detail as I can on what approach we recommend that will scale well with Nakama with these kinds of requirements but first some context. Nakama’s storage engine API supports key-value batch gets, updates, and deletes as well as listings to return a range of objects in a collection (which optionally belong to a specific user). We don’t have an official partial update API yet or the option to filter within the contents … In the future we plan to add JSON path support to perform partial updates as an official API in the storage engine. --- _[View the full topic](https://forum.heroiclabs.com/t/storage-partial-update-by-rest-api/466)._