> For the complete documentation index, see [llms.txt](https://use.temporal.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://use.temporal.xyz/nozomi/send-bundle/curl.md).

# cURL

The body is the binary bundle: each signed transaction prefixed with its length as a big-endian `u16`. Build it with the encoder from the [JavaScript](/nozomi/send-bundle/javascript.md) page, or with the shell below from base64-encoded signed transactions.

```bash
# tx1.b64 and tx2.b64 hold the base64 of each signed transaction; tx1 carries the tip.
: > bundle.bin
for f in tx1.b64 tx2.b64; do
  base64 -d "$f" > tx.bin
  len=$(stat -c %s tx.bin)
  printf "$(printf '\\x%02x\\x%02x' $((len >> 8)) $((len & 255)))" >> bundle.bin
  cat tx.bin >> bundle.bin
done

curl -X POST \
  "https://nozomi.temporal.xyz/api/sendBundle?c=YOUR_API_KEY" \
  -H "Content-Type: application/octet-stream" \
  --data-binary @bundle.bin
```

`200` with an empty body means the whole bundle was accepted. Any other status means nothing was sent; the body says why (see [Response](/nozomi/send-bundle.md#response)).


---

# 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://use.temporal.xyz/nozomi/send-bundle/curl.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.