
If you are doing a mass import of Items, you don’t need to do them one at a time. The same is true for update. You can do multiple edits at once through the REST API. In general, it's much more efficient to do things in batch because it cuts down on network latency.
If you’ve added an Item through the API, you probably noticed that the POST URL takes an array of ItemDetail objects. Even if you are just adding a single Item, you still have to put it in an array. To do a batch add, just include multiple objects in the array.
For Item updates, there are two endpoints: one for batch and one for single items. There is not much of a downside to using the batch endpoint for all item edits, even if it's just a single item. Just like with batch add, batch edit takes an array of ItemDetail objects. The only difference is that the objects must have ID values.
Example JSON of setting CITY=Paris on two Items:
| [ {"id":2913,"fields":{"CITY":"Paris"}}, {"id":2912,"fields":{"CITY":"Paris"}} ] |
All REST calls are transacted unless documented otherwise. So batch Add/Edit will either all succeed or all fail.
The limit is 10 Items at a time for batch add or edit. We’re starting out conservative, but we may decide to increase the limit in the future. It’s still 90% better than doing things one at a time.

Leave a Reply