> 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/solana/fast-landing/http-api.md).

# HTTP transaction submission

## Introduction

* **Base URL:** Use a [regional endpoint](/node1-docs/solana/fast-landing/endpoints.md), such as `https://ny.node1.me`.
* **Authentication:** Most endpoints require an API key in the request header, except for a few endpoints related to tips.
* **Data Format:** JSON-RPC requests use JSON, while HTTP V2 accepts the raw bytes from bincode::serialize(\&vtx).

## Authentication

In the request header, add the API key:

`api-key: YOUR_ACCOUNT_UUID`

Create an account at <https://node1.me> to receive an Account UUID and 2 TPS for Node1 Landing Service automatically. Use that UUID as the API key; request higher TPS through Discord.

## Send Transactions

### 🔗 JSON-RPC 2.0 Submit

● cURL Sample:

```bash
curl -X POST "https://ny.node1.me" \
-H "Content-Type: application/json" \
-H "api-key: YOUR_ACCOUNT_UUID" \
-d '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "sendTransaction",
  "params": [
    "YOUR_BASE64_ENCODED_TRANSACTION"
  ]
}'
```

● Success:

```json
{
  "jsonrpc": "2.0",
  "result": "5XHA7ofPAf3FaLUAY3kT52c...",
  "id": 1
}
```

### ⚡ HTTP V2 Raw Binary Submit

Send the serialized VersionedTransaction bytes directly to a regional /v2 endpoint. Keep the api-key header, and use the result of bincode::serialize(\&vtx) as the request body.

`Endpoint example: http://fra.node1.me/v2`

● Rust Sample:

```rust
let send_result = client.post("http://fra.node1.me/v2")
    .header("api-key", "YOUR_ACCOUNT_UUID")
    .body(bincode::serialize(&vtx).unwrap())
    .send().await;
```


---

# 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/solana/fast-landing/http-api.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.