> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/blynk.cloud/device-https-api/update-multiple-datastreams-api.md).

# Update Multiple Datastreams Simultaneously

Update multiple Datastreams of a single device with one GET request. It can help with saving the data volume for cellular devices.

{% hint style="warning" %}
Use such update for Map Widget in Blynk.Console so that all datapoints have same timestamp for data and coordinates.
{% endhint %}

## Batch update

<mark style="color:blue;">`GET`</mark> `https://{server_address}/external/api/batch/update?token={token}&{pin1}={value1}&{pin2}={value2}`

{% swagger-response status="400" description="Could not find a device token or Wrong pin format or Value doesn't match the Datastream data type" %}

```
{"error":{"message":"Invalid token."}}

or

{"error":{"message":"Wrong pin format."}}

or

{"error":{"message":"Value doesn't match the Datastream data type"}}
```

{% hint style="info" %}
You can get the **Device auth token** in [Device info](https://bit.ly/BlynkSimpleAuth).
{% endhint %}

You can also use Blynk.Edgent API to [send data with the same timestamp](https://docs.blynk.io/en/blynk.cloud/device-https-api/pages/gtxmxlHXv0MLxlHumL3A#blynk.begingroup-blynk.endgroup).


---

# 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://docs.blynk.io/en/blynk.cloud/device-https-api/update-multiple-datastreams-api.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.