> For the complete documentation index, see [llms.txt](https://api.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.dataloy.com/api-release-8.23/user-guides/enterprise-functionality/bulk-update-increment.md).

# Bulk Update Increment

Bulk Update Increment allows you to update multiple fields on multiple objects at once. With this endpoint multiple objects values can be set individually in bulk.

Use this endpoint to update multiple objects in one call by sending a JSON array of object keys and their new field values.

The endpoint to use is:

```
http://{host}/ws/rest/{ResourceName}/bulkUpdateIncrement
```

Passing, to the specified resource, a JSON array of entries, each containing:

* `key`: the primary key of the object
* one or more field names with the new value to set

Example payload:

```json
[
  { 
  "key": 77441913, 
  "foBallast": 10, "foLoaded": 15 
  },
  { 
    "key": 77443840,
    "foBallast": 12, "foLoaded": 20
  }
]
```

* Object `77441913` will have its `foBallast` field set to 10 and its `foLoaded` field set to 15.
* CommentShare feedback on the editorObject `77443840` will have its `foBallast` field set to 12 and its `foLoaded` field set to 20.

{% hint style="info" %}
**Note:** Each entry must include a `key` and at least one other field to update.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://api.dataloy.com/api-release-8.23/user-guides/enterprise-functionality/bulk-update-increment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
