> 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-feed/robinhood-feed-connection.md).

# Connection Guide

Use the Account UUID associated with your active Feed subscription. Both connection modes use the same Account UUID and Feed subscription. See [plans and activation](/node1-docs/robinhood/robinhood-feed.md).

Region: Ohio · Protocol: WebSocket (ws)

## Choose a format

**`/tx/<account_uuid>` is the faster connection for transaction data. `/feed/<account_uuid>` preserves the original Feed format and is intended for Nitro node acceleration.**

> **Node prerequisite:** Before switching to Node1 `/feed/`, you must first synchronize the node to the latest blocks through the official Robinhood Feed.

| Connection mode  | Path                   | Message format                              | Use case                                                   |
| ---------------- | ---------------------- | ------------------------------------------- | ---------------------------------------------------------- |
| Transaction Feed | `/tx/<account_uuid>`   | One transaction per message                 | Faster delivery for bots and custom transaction processing |
| Native Feed      | `/feed/<account_uuid>` | Original Feed format: one block per message | Robinhood Chain Nitro nodes                                |

Replace `<account_uuid>` with your Account UUID, without the angle brackets.

## Transaction Feed

```
ws://ohio.robinhood-feeder.node1.me/tx/<account_uuid>
```

Node1 splits the stream into individual transaction messages. Unlike the original block-based Feed, each message contains one transaction.

With wscat installed:

```bash
wscat -c "ws://ohio.robinhood-feeder.node1.me/tx/<account_uuid>"
```

## Native Feed (Nitro compatible)

```
ws://ohio.robinhood-feeder.node1.me/feed/<account_uuid>
```

This mode preserves the original Feed format, with one block per message, for Nitro-compatible consumers.

Include the following request header in the WebSocket handshake:

```http
Arbitrum-Feed-Client-Version: 2
```

With wscat installed:

```bash
wscat -c "ws://ohio.robinhood-feeder.node1.me/feed/<account_uuid>" \
  -H "Arbitrum-Feed-Client-Version: 2"
```

### Use with an existing Robinhood Chain Nitro node

1. Use the official Robinhood Feed to synchronize your node to the latest blocks.
2. Confirm the node has caught up before switching.
3. Replace its Feed input URL with the Node1 `/feed/` address below and ensure the required version header is sent:

```
--node.feed.input.url="ws://ohio.robinhood-feeder.node1.me/feed/<account_uuid>"
```

Ensure the node's WebSocket handshake sends `Arbitrum-Feed-Client-Version: 2`. This is a request header, not a URL query parameter. Use `/feed/` for Nitro's original-format input; `/tx/` has a different message format.

Restart the node after saving the configuration and check its logs for a successful Feed connection and incoming data. If the connection fails, check the UUID, subscription validity, required version header, and network connectivity.

## Connection errors

If the connection request is rejected, check the HTTP status code returned during the WebSocket handshake.

| Status code | Reason                                                                                                                  |
| ----------- | ----------------------------------------------------------------------------------------------------------------------- |
| `400`       | Missing or invalid version header, or a version below `2`; malformed request `sequence`; malformed WebSocket handshake. |
| `401`       | Invalid token, or the subscription is not yet active, has expired, or has been revoked.                                 |
| `404`       | The request path does not match a supported `/feed` or `/tx` endpoint.                                                  |
| `429`       | The connection limit for the account has been exceeded.                                                                 |
| `503`       | The subscription authorization cache is not ready, or has expired and is unavailable.                                   |


---

# 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-feed/robinhood-feed-connection.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.