# API v2

A faster alternative to JSON-RPC that eliminates JSON parsing overhead and CORS preflight latency. Recommended for browser clients and performance-sensitive backends.

## Request

| Field        | Value                                    |
| ------------ | ---------------------------------------- |
| Method       | `POST`                                   |
| Path         | `/api/sendTransaction2?c=<YOUR_API_KEY>` |
| Content-Type | `text/plain`                             |
| Body         | Base64-encoded transaction bytes         |

## Response

Returns an empty body with `200 OK` on success. **Does not return a transaction signature** — track signatures client-side before submitting.

## Why Use API v2

| Advantage         | Detail                                          |
| ----------------- | ----------------------------------------------- |
| No CORS preflight | Saves 50–100ms per request from browser clients |
| Faster encoding   | Base64 is faster to encode/decode than base58   |
| Smaller payload   | No JSON wrapper, plain text body                |
| Lower overhead    | No JSON parsing on the server side              |

## When to Use

Use API v2 when you don't need the transaction signature returned in the response, and want the lowest possible submission latency. Ideal for browser-based applications and high-frequency backends.

If you need a transaction signature in the response, use [JSON-RPC](/nozomi/transaction-submission-json-rpc.md) instead.


---

# Agent Instructions: 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:

```
GET https://use.temporal.xyz/nozomi/transaction-submission-api-v2.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.