> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/13-11-2026-trade-execute-bridge-input-amounts.md).

# 13-11-2026: Execute Reports the Sent Amount on Cross-Chain Swaps

**Affected endpoint:** `POST /api/v1/trade/execute`

On a cross-chain swap, Execute now waits for the source-chain transaction to land, for up to about 25 seconds, as it already does for same-chain swaps ([05-11-2026](https://docs.nansen.ai/api/changelog/05-11-2026-trade-execute-executed-amounts.md)). Send `to_chain` so the swap is recognised as cross-chain.

| Field                     | On a cross-chain swap                                                                                                                        |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| `confirmed`               | `true` when the source-chain transaction landed before the response. It does **not** mean the bridge completed                               |
| `inputMint`, `inAmount`   | The token the wallet sent on the source chain and how much, in base units, network fees excluded                                             |
| `outputMint`, `outAmount` | Always `null`. Use [Bridge Status](https://docs.nansen.ai/api/trade/spot-trading/bridge-status.md) for what arrived on the destination chain |

**Slower responses:** cross-chain executes take longer, usually by under 2 seconds and by up to 25 seconds on chains with slow blocks. Use an HTTP timeout of at least 60 seconds, and send `quote_id` so that a retry after a client timeout returns `409` instead of broadcasting a second trade.

**Behaviour change:** a cross-chain swap whose source-chain transaction reverted is now reported as `status: "Failed"`, with its transaction hash, when the revert is seen before the response. It was previously reported as `"Success"`.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/api/changelog/13-11-2026-trade-execute-bridge-input-amounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
