> 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-send-transaction.md).

# Send Transaction

[Endpoints, Account UUID, and rate limits](/node1-docs/robinhood/robinhood-landing.md).

Sign the transaction locally for Robinhood Chain, chain ID 4663. Supported formats are EIP-155 protected legacy, EIP-2930 type-1, and EIP-1559 type-2 transactions. Keep your private key in your own wallet or signing service.

Submit the signed transaction hex as the only item in params using POST / and the JSON-RPC method robinhood\_send\_raw\_transaction. The service does not sign transactions or provide a general-purpose chain RPC.

## cURL example

```bash
curl -X POST 'https://robinhood-ohio-2b.node1.me/' \
  -H 'Authorization: Bearer <ACCOUNT_UUID>' \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"robinhood_send_raw_transaction","params":["0x<SIGNED_TRANSACTION>"]}'
```

This example uses Ohio 2B. To use Ohio 2C or SFO3, replace the request URL with its address in the [service overview](/node1-docs/robinhood/robinhood-landing.md); the method and parameters stay the same. Replace the UUID and transaction placeholders with your own values. Use the complete signed transaction hex, remove the placeholder angle brackets, and keep a single 0x prefix.

## Submission acknowledgement

Updated nodes return HTTP 202 immediately after local validation, authentication, rate checks, and queue admission, with `x-node1-submission-state: queued`. They do not wait for a sequencer response. The result hash acknowledges local acceptance, not completed forwarding or block inclusion.

A single request counts as one transaction. Standard paid accounts share [transaction-based quota](/node1-docs/robinhood/robinhood-landing.md) with plain text and batches.

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.

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x<TRANSACTION_HASH>",
  "message": "Successfully forwarded"
}
```

[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-send-transaction.md?ask=<question>&goal=<endgoal>
```

`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.