---
title: "Sign a quote for swap execution"
method: POST
path: "/rfq/sign"
tags: ["Quote"]
---

# Sign a quote for swap execution

`POST /rfq/sign`

This endpoint plays a pivotal role in the preparation and execution of secure asset swaps on the blockchain. By providing a Quote ID and a destination address, users can initiate the signing process, resulting in the generation of the essential signature and transaction data. This signature and data package, in turn, is integral for ensuring the validity and security of asset transfers within the blockchain network.

## Request body

- SignRequest
  - `quote_id` string, uuid, required — The id of the quote returned in quote endpoint
  - `destination_address` string, required — Address that will receive the output token
  - `sender_address` string — For DEX aggregator partners that are using their own smart contract to mediate the interaction between users and Blade. Aggregators should use the address of the account that they will pull tokens from (i.e., the EOA user address) as opposed to the address of their deployed contract. By default, `destination_address` will be used.
  - `aux_data` string — For use with the calldata swap feature, it can be set to any string and is used for identification purposes in the event logs. By default is` 0x436c697070657200000000000000000000000000000000000000000000000000` that is the representation of `Clipper`
  - `calldata` boolean — Send this as true if we want to get the bytes representation of the swap in the response. Client can use this to be sent directly to the pool contract for execution.
  - `native_input` boolean — If the input token is native (e.g. raw ETH), this value must be true. This will use the `sellEthForToken` contract function and will take the `msg.value` for the input. e.g `ETH -> USDC`. This field is mutually exclusive with `native_output`.
  - `native_output` boolean — If the output token is native (i.e. raw ETH), this value must be true. This will use the `sellTokenForEth` contract function. e.g `USDC -> ETH`. This field is mutually exclusive with `native_input`.

## Response `200`

Quote signed successfully

- SignResponse
  - `chain_id` integer, required — Represents the ID of the chain
  - `input_asset_address` string, required — Contract address of the asset you want to provide for the swap
  - `output_asset_address` string, required — Contract address of the asset you want to receive in the swap
  - `input_amount` string, required — Amount of assets to be exchanged
  - `output_amount` string, required — Amount of assets you will receive in the exchange
  - `good_until` string, required — Number of seconds that quotes live. It can also contained a packed representation of the state
  - `destination_address` string, required — Address will receive the output token
  - `signature` EIP2098Signature, required — A EIP 2098 'short signature' representation for the signature from the Blade Exchange server
    - `v` integer, required — Recovery identifier
    - `r` string, required — ECDSA signature r
    - `s` string, required — ECDSA signature s
  - `clipper_exchange_address` string, required — Blade contract address of the pool, is the address used when executing a transaction
  - `calldata` string — Bytes representation of the swap function and parameters to be sent directly to the `clipper_exchange_address` for execution. Only present when `calldata=true` in request.

## Other responses

- `400` — Bad Request - Invalid data in the request
- `401` — Unauthorized - Missing or invalid API key. Ensure you include a valid `x-api-key` header.
- `403` — Forbidden Error - Access denied
- `422` — Invalid input data
- `500` — Internal Server Error
- `503` — External Service Error

---

[API](https://skmtc.net/sushi/apis/blade-api.md) · [All operations](https://skmtc.net/sushi/apis/blade-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sushi/blade-api/versions/24cab97a081a/schema)