> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/robinhood/robinhood-landing/robinhood-batch.md). # Batch Transactions [Endpoints, Account UUID, and rate limits](/node1-docs/robinhood/robinhood-landing.md). Use robinhood\_sendBatchTransaction with a flat params array of 1–10 signed transaction strings. The whole HTTP body must fit within the node’s configured limit (at most 256 KiB). All transactions are checked before any are forwarded. ```json { "jsonrpc": "2.0", "id": 2, "method": "robinhood_sendBatchTransaction", "params": [ "0x", "0x" ] } ``` ## Quota and acknowledgement Standard paid accounts share [transaction-based quota](/node1-docs/robinhood/robinhood-landing.md) across raw, plain text, and batch. A 10-transaction batch consumes 10 credits. If the whole batch does not fit the quota, it receives HTTP 429 without sending a subset. Free accounts retain a separate batch request count. The service persists a local batch receive record, completes rate checks and queue admission, then returns HTTP 202. It does not wait for a sequencer response or the per-transaction sending intervals within the HTTP request. Records are uploaded to the database asynchronously. The response contains `result.batch_id` and `result.transactions` in input order. Each `status: queued` acknowledges local acceptance; `tx_hash` is the transaction hash, `duplicate` indicates a deduplication hit, and `retry` gives retry guidance. Inspect every item: HTTP 202 does not mean all transactions succeeded. See [Responses & Retries](/node1-docs/robinhood/robinhood-landing/robinhood-responses.md) for a complete example and failure cases. The display field `message` is `"Successfully forwarded"`. It appears at the top level for single JSON-RPC and plain-text responses, and on each `queued` transaction item in a batch. This is presentation text: the service still returns HTTP 202 after local queue admission, without waiting for socket writes or sequencer acknowledgement. It does not confirm block inclusion. Clients should use the status, hash, and error fields rather than this display text to determine transaction state. ## Sending schedule Transactions within a batch are scheduled in input order in the background, with a target 5 ms interval and without waiting for the preceding acknowledgement. Different batches may interleave. Batches do not provide atomic on-chain execution or guarantee network arrival, inclusion order, or execution success. Passing the whole-batch quota check does not guarantee that every subsequent forwarding path will succeed. [Response handling and retry rules →](/node1-docs/robinhood/robinhood-landing/robinhood-responses.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://node1.gitbook.io/node1-docs/robinhood/robinhood-landing/robinhood-batch.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.