---
title: "Broadcast a signed Solana transaction"
method: POST
path: "/svm/execute"
---

# Broadcast a signed Solana transaction

`POST /svm/execute`

## Request

- Base URL: `https://swap.vurto.cc/v1`
- URL: `https://swap.vurto.cc/v1/svm/execute`
- Auth: none required

How you call this depends on whether the build returned an executionRef. Absent: we assembled the route, so send only signedTransaction and we broadcast it. Present: the route came from the meta-aggregator, an RFQ leg can involve a market maker with last-look rights, and it refuses a transaction altered after quoting, so it has to go back through it to land. Broadcasting that one yourself raises no error, it simply never confirms. Either way this is a relay, not custody: the transaction arrives already signed, so all this can do is deliver it or not.

## Request body

- object
  - `signedTransaction` string, required: base64 of the fully signed transaction.
  - `executionRef` string: Only when the build carried one.

## Response `200`

{signature, status}. status "pending" means the network accepted the send, which is not the same as having put it in a block.

## Other responses

- `400`: invalid_execution — the signed transaction is missing or malformed
- `502`: execution_failed — the network or the aggregator refused it

---

[API](https://skmtc.dev/vurto/apis/vurto-swap-public-api.md) · [All operations](https://skmtc.dev/vurto/apis/vurto-swap-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/vurto/apis/vurto-swap-public-api/revisions/423be3a193b5?raw)