> For the complete documentation index, see [llms.txt](https://docs.swapkit.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swapkit.dev/api-reference/v3-limit-place-an-order.md).

# /v3/limit - Place an order

Price a pair, build the artifact the wallet signs, and submit the signature or deposit hash that puts the order on the book.

Steps 1–3 of the order flow. Read [Signing models](https://docs.swapkit.dev/api-reference/v3-limit-place-and-manage-limit-orders.md#signing-models) first: which of the two shapes `/v3/limit/build` returns decides most of what this page asks you to handle.

Once an order is resting, [Manage and cancel orders](https://docs.swapkit.dev/api-reference/v3-limit-manage-and-cancel-orders.md) covers reading and cancelling it.

<figure><picture><source srcset="https://1967725871-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl88kbsjWGhgdARxzgqCE%2Fuploads%2Fgit-blob-e43c1f927db0cdfe8097a8204351339c19a09b87%2Flimit-order-flow-dark.svg?alt=media" media="(prefers-color-scheme: dark)"><img src="https://1967725871-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl88kbsjWGhgdARxzgqCE%2Fuploads%2Fgit-blob-58f7ecdb6be965ab01486355dbc8657ed355bf22%2Flimit-order-flow.svg?alt=media" alt="Placing a limit order. 1: POST /v3/limit/quote. 2: POST /v3/limit/build, which returns either typedData for the wallet to sign or tx for the wallet to broadcast; if isApproved is false, broadcast approvalTx first. 3: POST /v3/limit/submit with the signature or the depositTxHash. The order then rests until it is filled, cancelled or expires. Steps 4 to 7 read and cancel orders."></picture><figcaption><p>Steps 1–3 on this page.</p></figcaption></figure>

***

## 1. Price the pair

**Method:** `POST`\
**URL:** `https://api.swapkit.dev/v3/limit/quote`

Prices the pair, measures the limit against the market, and returns a `routeId` for `/v3/limit/build`.

### Request schema

<table><thead><tr><th width="200">Parameter</th><th width="150">Type</th><th width="100">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>sellAsset</code></td><td><code>string</code></td><td>Yes</td><td>Asset to sell, e.g. <code>"ETH.ETH"</code>.</td></tr><tr><td><code>buyAsset</code></td><td><code>string</code></td><td>Yes</td><td>Asset to buy, e.g. <code>"BTC.BTC"</code>.</td></tr><tr><td><code>sellAmount</code></td><td><code>decimal string</code></td><td>No</td><td>Send <strong>any two</strong> of <code>sellAmount</code> / <code>buyAmount</code> / <code>limitPrice</code>; the third is derived. <strong>Human-readable, not base units</strong>: 10 USDT is <code>"10"</code>.</td></tr><tr><td><code>buyAmount</code></td><td><code>decimal string</code></td><td>No</td><td>Same rules as <code>sellAmount</code>.</td></tr><tr><td><code>limitPrice</code></td><td><code>decimal string</code></td><td>No</td><td><code>buyAsset</code> per 1 <code>sellAsset</code>.</td></tr><tr><td><code>sourceAddress</code></td><td><code>string</code></td><td>No</td><td>Screened for AML now, and pre-filled into the <code>/v3/limit/build</code> request.</td></tr><tr><td><code>destinationAddress</code></td><td><code>string</code></td><td>No</td><td>Same as <code>sourceAddress</code>.</td></tr><tr><td><code>affiliateFee</code></td><td><code>int</code> (0–1000 bps)</td><td>No</td><td>Overrides the API key's default. <code>0</code> when your key has no affiliate set up for the routed provider. NEAR Intents allows about 480 bps of fees in total.</td></tr><tr><td><code>expiresAt</code></td><td><code>int</code> (unix seconds)</td><td>No</td><td>Only pre-fills the <code>/v3/limit/build</code> request; not checked here. Defaults to now + 3 days.</td></tr><tr><td><code>providers</code></td><td><code>enum[]</code></td><td>No</td><td>Restrict routing to these providers. Only <code>ONEINCH</code>, <code>HARBOR</code> and <code>NEAR</code> run limit orders; other provider names are skipped.</td></tr></tbody></table>

{% hint style="info" %}
Asset identifiers follow the same nomenclature as the rest of the API — `Chain.Asset` (`"BTC.BTC"`) or `Chain.Asset-ContractAddress` (`"ETH.USDC-0xA0b8…"`). See [`/tokens`](https://docs.swapkit.dev/api-reference/tokens-list-and-search-supported-tokens.md).
{% endhint %}

### Response schema

**Top level**

<table><thead><tr><th width="200">Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>quoteId</code></td><td><code>string</code></td><td>UUID of this quote.</td></tr><tr><td><code>routes</code></td><td><code>LimitRoute[]</code></td><td>Always one route.</td></tr></tbody></table>

**Per route**

<table><thead><tr><th width="200">Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>routeId</code></td><td><code>string</code></td><td>UUID of this route. Pass it to <code>/v3/limit/build</code>.</td></tr><tr><td><code>provider</code></td><td><code>enum</code></td><td>The provider SwapKit chose.</td></tr><tr><td><code>sellAsset</code>, <code>buyAsset</code></td><td><code>string</code></td><td>Echoed from the request.</td></tr><tr><td><code>sellAmount</code>, <code>buyAmount</code>, <code>limitPrice</code></td><td><code>decimal string</code></td><td>Resolved values, including the one you didn't send.</td></tr><tr><td><code>spotPrice</code></td><td><code>decimal string</code></td><td>Current market price.</td></tr><tr><td><code>effectiveFillPrice</code></td><td><code>decimal string</code></td><td>The price the market must reach for the order to fill: <code>spotPrice</code> plus the fee gap. The gap is <code>takerFeeBps + integratorFeeBps</code> on 1inch and <code>takerFeeBps</code> on Harbor. NEAR Intents reports <code>takerFeeBps: 0</code>, so there it equals <code>spotPrice</code>. Compare limits against this, not <code>spotPrice</code>.</td></tr><tr><td><code>takerFeeBps</code></td><td><code>number</code></td><td>The provider's taker fee, in bps. Excludes <code>integratorFeeBps</code>.</td></tr><tr><td><code>spotPriceDeviationBps</code></td><td><code>number</code></td><td>Signed bps distance of <code>limitPrice</code> from <code>effectiveFillPrice</code>.<br><strong>Positive</strong>: the order rests until the market moves.<br><strong>Zero or negative</strong>: it fills immediately, at a worse rate than a market swap.</td></tr><tr><td><code>minExpirationSeconds</code>, <code>maxExpirationSeconds</code></td><td><code>number</code></td><td>Allowed range for <code>expiresAt − now</code> at <code>/v3/limit/build</code>. Today: from 60 s (1inch, Harbor) or 300 s (NEAR Intents) up to one year.</td></tr><tr><td><code>integratorFeeBps</code></td><td><code>number</code></td><td>Your affiliate fee on this route.</td></tr><tr><td><code>warnings</code></td><td><code>Warning[]</code></td><td>See <a href="#warnings">Warnings</a>.</td></tr><tr><td><code>nextActions</code></td><td><code>object[]</code></td><td>One entry: the <code>/v3/limit/build</code> request, ready to send. If you didn't send addresses, replace its placeholder addresses first.</td></tr></tbody></table>

### Warnings

`warnings[]` is always present, may be empty, and carries through to the `/v3/limit/build` response. At most one price warning fires per quote:

* `limitPriceBelowSpot` — `spotPriceDeviationBps ≤ -100`. The limit is 1% or more below `effectiveFillPrice`, so the order fills immediately at a clearly worse rate than a market swap.
* `limitPriceWithinFeeGap` — `-100 < spotPriceDeviationBps ≤ 0`, with a non-zero fee gap. It also fills immediately, only modestly off-market. Raising the limit by `|spotPriceDeviationBps|` bps or more makes it rest.

Both mean the order fills on submission rather than resting, so show them before the user signs. One more warning is independent of price:

* `limitOrderNotionalTooSmall` — the sell-side USD value is below what the provider's fillers usually take (NEAR Intents: about $20). The order rests, but may never fill before it expires and is refunded. Skipped when the sell asset has no USD price.

{% hint style="info" %}
**Warnings never block anything.** Whatever `warnings[]` holds, the quote stays valid and the order placeable — if a user should stop and reconsider, that gate has to live in your own UI.
{% endhint %}

#### Rendering a warning

```json
{
  "code": "limitPriceBelowSpot",
  "display": "2.40% below effective fill price",
  "tooltip": "Your limit price is more than 1% below the effective fill price (spot + taker fees). The order will fill immediately at a worse rate than a market swap."
}
```

* **`display`** — a short label for the user, already carrying this quote's numbers. Show it as-is.
* **`tooltip`** — a longer explanation for a hover or tap. Optional.
* **`code`** — for your logic, such as asking for a second confirmation on `limitPriceBelowSpot`. An open enum: fall back to `display` for codes you don't know.

### Errors

<table><thead><tr><th width="80">Status</th><th width="270">Error code</th><th>Scenario</th></tr></thead><tbody><tr><td>400</td><td><code>validation_error</code></td><td>Invalid body: not exactly two of <code>sellAmount</code> / <code>buyAmount</code> / <code>limitPrice</code>, a malformed or zero amount, <code>sellAsset</code> equal to <code>buyAsset</code>, or an unknown <code>providers</code> value. The message names the field.</td></tr><tr><td>400</td><td><code>insufficientLiquidity</code></td><td>No market rate for the pair, or a zero one. Retry.</td></tr><tr><td>400</td><td><code>invalidSourceAddress</code></td><td><code>sourceAddress</code> isn't valid on the sell chain.</td></tr><tr><td>400</td><td><code>invalidDestinationAddress</code></td><td><code>destinationAddress</code> isn't valid on the buy chain.</td></tr><tr><td>400</td><td>Other address codes</td><td><code>invalidSellAssetAddress</code>, <code>invalidBuyAssetAddress</code>, <code>xrpAddressRequiresTag</code>, <code>litecoinMwebAddressUnsupported</code>: an address breaks a chain-specific rule.</td></tr><tr><td>400</td><td><code>limitOrderUnsupportedPair</code></td><td>No provider supports this pair.</td></tr><tr><td>400</td><td><code>limitOrderProviderUnsupported</code></td><td><code>providers</code> names none of <code>ONEINCH</code>, <code>HARBOR</code> or <code>NEAR</code>, or is empty.</td></tr><tr><td>400</td><td>Provider codes (NEAR Intents)</td><td>NEAR Intents' own rejection, such as <code>quoteError</code> for an amount below its minimum.</td></tr><tr><td>401</td><td><code>apiKeyInvalid</code></td><td>Missing <code>x-api-key</code>.</td></tr><tr><td>401</td><td><code>unauthorized</code></td><td>Unrecognised <code>x-api-key</code>.</td></tr><tr><td>451</td><td><code>isSanctionedAddress</code></td><td>An address is on a sanctions or risk list.</td></tr><tr><td>502</td><td><code>limitOrderProviderError</code></td><td>1inch failed while pricing (rate limit, 5xx or transport). Retry.</td></tr><tr><td>503</td><td><code>limitOrderActionUnavailable</code></td><td>The action is switched off for one of the pair's chains. Can clear without a change on your side.</td></tr></tbody></table>

***

## 2. Build the signing artifact

**Method:** `POST`\
**URL:** `https://api.swapkit.dev/v3/limit/build`

Screens both addresses, builds the order with the provider, checks the token approval, and saves the order as `PENDING`.

### Request schema

<table><thead><tr><th width="200">Parameter</th><th width="150">Type</th><th width="100">Required</th><th>Description</th></tr></thead><tbody><tr><td><code>routeId</code></td><td><code>string</code></td><td>Yes</td><td>From <code>/v3/limit/quote</code>.</td></tr><tr><td><code>sourceAddress</code></td><td><code>string</code></td><td>Yes</td><td>Address on the sell chain that funds the order. Becomes <code>maker</code>.</td></tr><tr><td><code>destinationAddress</code></td><td><code>string</code></td><td>Yes</td><td>Address on the buy chain that receives the proceeds. Becomes <code>receiver</code>.</td></tr><tr><td><code>expiresAt</code></td><td><code>int</code> (unix seconds)</td><td>Yes</td><td>An absolute time, but <code>expiresAt − now</code> must fall within the quote's <code>[minExpirationSeconds, maxExpirationSeconds]</code>.</td></tr><tr><td><code>allowPartialFill</code></td><td><code>bool</code></td><td>No</td><td>1inch only, and must stay <code>true</code> (the default). Harbor and NEAR Intents ignore it.</td></tr><tr><td><code>allowMultipleFills</code></td><td><code>bool</code></td><td>No</td><td>Same as <code>allowPartialFill</code>.</td></tr></tbody></table>

### Build response schema

<table><thead><tr><th width="200">Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>orderId</code></td><td><code>string</code></td><td>UUID of the order. Pass it to every later call.</td></tr><tr><td><code>orderHash</code></td><td><code>string</code></td><td>The provider's order identifier: <code>0x</code>-prefixed on 1inch and Harbor, the 1Click order id on NEAR Intents.</td></tr><tr><td><code>typedData</code></td><td><code>object</code> or <code>null</code></td><td>Payload for the wallet to sign. Signed-intent orders only, otherwise <code>null</code>. <a href="#the-typeddata-object">See below</a>.</td></tr><tr><td><code>tx</code></td><td>varies, or <code>null</code></td><td>Transaction to broadcast. Deposit orders only, otherwise <code>null</code>. <a href="#the-tx-field">See below</a>.</td></tr><tr><td><code>txMeta</code></td><td><code>object</code> or <code>null</code></td><td>How to broadcast <code>tx</code>; <code>null</code> when <code>tx</code> is. <a href="#the-tx-field">See below</a>.</td></tr><tr><td><code>depositAddress</code></td><td><code>string</code> (optional)</td><td>Harbor and NEAR Intents only. Where the funds land — informational; fund the order by broadcasting <code>tx</code>. <a href="#the-deposit-fields">See below</a>.</td></tr><tr><td><code>depositAmount</code></td><td><code>decimal string</code> (optional)</td><td>Harbor and NEAR Intents only. Exactly what <code>tx</code> deposits, human-readable. <a href="#the-deposit-fields">See below</a>.</td></tr><tr><td><code>depositMemo</code></td><td><code>string</code> (optional)</td><td>Every Harbor order, and NEAR Intents on Stellar: the memo that ties the deposit to the order. <a href="#the-deposit-fields">See below</a>.</td></tr><tr><td><code>isApproved</code></td><td><code>boolean</code> (optional)</td><td>Whether the token allowance is in place. Omitted when no approval applies. <a href="#the-isapproved-field">See below</a>.</td></tr><tr><td><code>approvalTx</code></td><td><code>object</code> (optional)</td><td>Approval to broadcast before the order. <a href="#the-approvaltx-object">See below</a>.</td></tr><tr><td><code>warnings</code></td><td><code>Warning[]</code></td><td>Carried over from the quote.</td></tr><tr><td><code>nextActions</code></td><td><code>object[]</code></td><td>The <code>/v3/limit/submit</code> request to send next.</td></tr></tbody></table>

### Response — the two signing models

You get exactly one of these two shapes — see [signing models](https://docs.swapkit.dev/api-reference/v3-limit-place-and-manage-limit-orders.md#signing-models).

{% tabs %}
{% tab title="Signed intent — typedData to sign" %}
**1inch, selling a token.**

```json
{
  "orderId": "3f2b8c1e-…",
  "orderHash": "0x…",
  "typedData": {
    "domain":      { },
    "types":       { "Order": [] },
    "primaryType": "Order",
    "message":     { }
  },
  "tx":     null,
  "txMeta": null,
  "isApproved": true,
  "warnings":   [],
  "nextActions": []
}
```

The wallet signs `typedData`, then you post the resulting signature to `/v3/limit/submit` as `{ orderId, signature }`.
{% endtab %}

{% tab title="Deposit — tx to broadcast" %}
**Harbor and NEAR Intents, and 1inch selling a native gas asset.** The example is a Harbor ETH deposit. A 1inch native sell has the same shape minus `depositAddress`, `depositAmount`, `depositMemo`, `txMeta.memo` and `isApproved`: its `tx` calls 1inch's native-order factory, which escrows the sell amount for the order.

```json
{
  "orderId": "3f2b8c1e-…",
  "orderHash": "0x…",
  "typedData": null,
  "tx": {
    "from":  "0x…",
    "to":    "0x…",
    "value": "…",
    "data":  "0x…"
  },
  "txMeta": {
    "txType":  "evm",
    "chainId": 1,
    "memo":    "o:…"
  },
  "depositAddress": "0x…",
  "depositAmount":  "10.5",
  "depositMemo":    "o:…",
  "isApproved": true,
  "warnings":   [],
  "nextActions": []
}
```

The wallet signs and broadcasts `tx`, then you post the on-chain hash to `/v3/limit/submit` as `{ orderId, depositTxHash }`.
{% endtab %}
{% endtabs %}

#### The `typedData` object

An EIP-712 document (`domain`, `types`, `primaryType`, `message`). Pass it to the wallet unmodified: the signature covers the exact payload.

On 1inch the domain is `"1inch Aggregation Router"` version `"6"`, and its `verifyingContract` is the same spender the [`approvalTx`](#the-approvaltx-object) approves.

#### The `tx` field

Its shape depends on the sell chain, and `txMeta` says how to handle it, as on `/v3/swap`:

<table><thead><tr><th width="200">Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>txMeta.txType</code></td><td><code>string</code></td><td>How to sign and broadcast <code>tx</code>. <code>"evm"</code> is <code>{ from, to, value, data }</code>, with <code>value</code> in wei as hex on a 1inch native sell and as a decimal string on Harbor and NEAR Intents — accept both. <code>"psbt"</code> is a base64 string. Other values name their chain (<code>"solana"</code>, <code>"near"</code>, <code>"tron"</code>, …). An open enum: refuse an unknown value rather than guess.</td></tr><tr><td><code>txMeta.chainId</code></td><td><code>number</code> (optional)</td><td>EVM chain id as a <strong>number</strong> (<code>1</code>, <code>42161</code>). Only when <code>txType</code> is <code>"evm"</code>.</td></tr><tr><td><code>txMeta.memo</code></td><td><code>string</code> (optional)</td><td>The order memo inside <code>tx</code>, to check before signing. Same as <code>depositMemo</code>; omitted when there's none.</td></tr></tbody></table>

#### The deposit fields

**Fund the order by broadcasting `tx`.** `depositAddress`, `depositAmount` and `depositMemo` are informational: show them, and check `tx` against them before signing. A 1inch native sell returns none of them.

They are not a recipe for a transfer you build yourself: a plain transfer to `depositAddress` carries no memo and can't be matched to the order.

{% hint style="danger" %}
**Never reuse a deposit, and never build one yourself.** Broadcast the `tx` each build returns. A reused address or memo credits the wrong order or none — and on memo-attributed routes the send still succeeds, so nothing looks wrong.
{% endhint %}

What ties a deposit to its order differs by route:

<table><thead><tr><th width="170">Route</th><th width="320">The order is identified by</th><th>Does depositAddress repeat across orders?</th></tr></thead><tbody><tr><td><strong>NEAR Intents</strong></td><td>A fresh <code>depositAddress</code>, minted on every <code>/v3/limit/build</code> — even for the same maker and pair.</td><td>Never. Sending to a previous order's address credits <em>that</em> order.</td></tr><tr><td><strong>Harbor</strong></td><td>The <code>o:</code> memo, returned as <code>depositMemo</code>, that <code>tx</code> carries — an argument to Harbor's router call on Ethereum, an <code>OP_RETURN</code> output on Bitcoin.</td><td>Always: it is Harbor's shared vault, which can also rotate between builds.</td></tr><tr><td><strong>Stellar on NEAR Intents</strong></td><td><code>depositMemo</code> (<code>MEMO_TEXT</code>) alone — mandatory, and unique per order.</td><td>Always: one address is shared across orders.</td></tr></tbody></table>

So don't cache an address or a memo, and don't key either by maker or by pair.

**Send exactly `depositAmount`.** Overpaying doesn't enlarge the order — the excess is refunded separately after the order resolves. Underpaying leaves it unfunded.

<details>

<summary>Why isn't <code>tx</code> addressed to <code>depositAddress</code>?</summary>

On several routes it legitimately targets something else, so don't reject a deposit on that alone:

* **Harbor on EVM** — `tx` calls Harbor's router, which forwards the value to the vault at `depositAddress` with the memo attached.
* **TON** — `tx.messages[0].address` is your own jetton wallet, carrying a little TON for gas. The real destination and amount are inside the base64 payload.
* **NEAR** — a token deposit calls the token's contract. Only a native `NEAR.NEAR` deposit is a plain transfer to `depositAddress`.

</details>

{% hint style="warning" %}
**`tx` goes stale fast** — in under two minutes on the quickest chains, so get the signature promptly. **Rebuilding isn't refreshing:** every `/v3/limit/build` is a new order, with its own `orderId` and deposit address or memo. Leave the stale one to [expire](https://docs.swapkit.dev/api-reference/v3-limit-place-and-manage-limit-orders.md#order-status-lifecycle).
{% endhint %}

`tx` is built against chain state — a recent blockhash, a nonce, selected UTXOs — and a wallet prompt left sitting, or a hardware-wallet flow, routinely outlives it.

#### The `approvalTx` object

Present when the maker's token allowance is below the order amount. Same shape as on [`/v3/swap`](https://docs.swapkit.dev/api-reference/v3-swap-obtain-swap-transaction-details.md#the-approvaltx-object). Broadcast it and wait for confirmation **before** signing or broadcasting the order.

<table><thead><tr><th width="200">Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>approvalTx.to</code></td><td><code>string</code></td><td>Token contract.</td></tr><tr><td><code>approvalTx.from</code></td><td><code>string</code></td><td>The user's wallet.</td></tr><tr><td><code>approvalTx.value</code></td><td><code>string</code></td><td>Always <code>"0"</code>.</td></tr><tr><td><code>approvalTx.data</code></td><td><code>string</code></td><td>Encoded <code>approve()</code> call.</td></tr><tr><td><code>approvalTx.gasLimit</code></td><td><code>string</code></td><td>Optional. Gas limit, as a hex quantity.</td></tr><tr><td><code>approvalTx.gasPrice</code></td><td><code>string</code></td><td>Optional. Legacy (type-0) gas price in wei, as a hex quantity.</td></tr></tbody></table>

#### The `isApproved` field

Only present when a token `approve()` is part of the flow:

<table><thead><tr><th width="200">Value</th><th>Meaning</th></tr></thead><tbody><tr><td><code>isApproved: true</code></td><td>Nothing to broadcast — but not proof the allowance exists (see below).</td></tr><tr><td><code>isApproved: false</code></td><td>Broadcast <a href="#the-approvaltx-object"><code>approvalTx</code></a> <strong>before</strong> signing the order.</td></tr><tr><td>Field omitted</td><td>No approval needed: a native sell, or a chain without allowances, such as a UTXO chain.</td></tr></tbody></table>

Tokens pulled through a router contract need an approval: 1inch, and Harbor's ETH.USDT deposits. NEAR Intents is funded by a plain transfer, so it never needs one, even for an ERC-20.

{% hint style="warning" %}
Branch on `isApproved === false`, not on falsiness: a missing `isApproved` means "nothing to broadcast", **not** `false`.
{% endhint %}

<details>

<summary>Why can <code>isApproved</code> be <code>false</code> for a token that's already approved?</summary>

It reports whether **this order** can be pulled, on the same amount- and spender-scoped terms as `/v3/swap` — see [How the allowance is read](https://docs.swapkit.dev/api-reference/v3-swap-obtain-swap-transaction-details.md#how-the-allowance-is-read). Approving 1 USDT and then building a 2 USDT order returns `false`, and an allowance granted for another provider doesn't carry over, because each provider pulls through its own contract.

It's advisory the other way too: if the allowance read fails, the build returns `true` rather than failing.

</details>

### Errors

<table><thead><tr><th width="80">Status</th><th width="270">Error code</th><th>Scenario</th></tr></thead><tbody><tr><td>404</td><td><code>limitOrderQuoteNotFound</code></td><td>Unknown or expired <code>routeId</code> — routes last a few minutes. Quote again.</td></tr><tr><td>400</td><td><code>validation_error</code></td><td>Invalid body. The message names the field.</td></tr><tr><td>400</td><td><code>limitOrderExpirationOutOfBounds</code></td><td><code>expiresAt</code> is outside the quote's expiration bounds. The message gives both.</td></tr><tr><td>400</td><td><code>limitOrderUnsupportedFillFlags</code></td><td>1inch: <code>allowPartialFill</code> or <code>allowMultipleFills</code> was <code>false</code>.</td></tr><tr><td>400</td><td><code>limitOrderUnsupportedPair</code></td><td>The provider can't build this pair. On 1inch: neither 1inch nor your key puts a fee on it, which 1inch orders can't express. Don't retry as-is.</td></tr><tr><td>400</td><td><code>limitOrderUnsupportedChain</code></td><td>The provider can't build on the sell chain, e.g. a 1inch native sell where 1inch has no native-order factory.</td></tr><tr><td>400</td><td><code>invalidSourceAddress</code>, <code>invalidDestinationAddress</code></td><td>An address isn't valid on its chain. <code>/build</code> re-checks both.</td></tr><tr><td>400</td><td><code>insufficientBalance</code></td><td>UTXO chains, Cardano, Sui and Tron: the maker address is empty, so there's nothing to build the deposit from. Fund it and rebuild.</td></tr><tr><td>400</td><td><code>sellAssetAmountTooSmall</code></td><td>Below the provider's minimum order size, given in the message. Unlike the <code>limitOrderNotionalTooSmall</code> warning, this blocks.</td></tr><tr><td>400</td><td><code>limitOrderRejected</code></td><td>The provider refused the order; the message gives its reason. On NEAR Intents, includes a delivery fee above 5% of the proceeds: place a larger order.</td></tr><tr><td>401</td><td><code>apiKeyInvalid</code>, <code>unauthorized</code></td><td>Missing or unrecognised <code>x-api-key</code>.</td></tr><tr><td>451</td><td><code>isSanctionedAddress</code></td><td>The full address screen flagged <code>sourceAddress</code> or <code>destinationAddress</code>.</td></tr><tr><td>500</td><td><code>limitOrderBuildFailed</code></td><td>The provider failed to build the order. On NEAR Intents, also fees above about 480 bps in total: lower <code>affiliateFee</code>.</td></tr><tr><td>502</td><td><code>limitOrderProviderError</code></td><td>NEAR Intents failed upstream (5xx or transport). Retry.</td></tr></tbody></table>

***

## 3. Submit the signed artifact

**Method:** `POST`\
**URL:** `https://api.swapkit.dev/v3/limit/submit`

Attaches the signature or the deposit tx hash and moves the order from `PENDING` to `SUBMITTED`. Sync moves it on to `OPEN` once the provider confirms it.

### Request schema

Send `signature` **or** `depositTxHash`, depending on which artifact `/v3/limit/build` returned.

<table><thead><tr><th width="200">Parameter</th><th width="150">Type</th><th width="160">Required for</th><th>Description</th></tr></thead><tbody><tr><td><code>orderId</code></td><td><code>string</code></td><td>All orders</td><td>From <code>/v3/limit/build</code>.</td></tr><tr><td><code>signature</code></td><td><code>string</code></td><td>Signed intent</td><td>Wallet signature over <code>typedData</code>. Relayed to the provider's orderbook.</td></tr><tr><td><code>depositTxHash</code></td><td><code>string</code></td><td>Deposit</td><td>Hash of the deposit transaction, exactly as the chain reports it. Comes back as <code>depositHash</code> on the order. Harbor lowercases it; NEAR Intents and 1inch store it as sent. <a href="#submitting-a-deposit-hash">See below</a>.</td></tr></tbody></table>

```json
// Signed intent — wallet signature over typedData
{ "orderId": "3f2b8c1e-…", "signature": "0x…" }

// Deposit — hash of the broadcast deposit transaction
{ "orderId": "3f2b8c1e-…", "depositTxHash": "0x… | …btc txid… | …base58 signature…" }
```

#### Submitting a deposit hash

A deposit order submits the **hash**, never a signature — even on Solana, where a transaction's *signature* **is** its identifier.

Send it exactly as the chain reports it. Solana's hash is base58 and TON's base64, both case-sensitive: lowercasing them, a habit from EVM, destroys the value, and the deposit is never matched to the order.

### Submit response schema

<table><thead><tr><th width="200">Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>orderId</code></td><td><code>string</code></td><td>UUID of the order.</td></tr><tr><td><code>orderHash</code></td><td><code>string</code></td><td>Same as on <code>/v3/limit/build</code>.</td></tr><tr><td><code>status</code></td><td><code>enum</code></td><td>Always <code>SUBMITTED</code> on success. See the <a href="https://docs.swapkit.dev/api-reference/v3-limit-place-and-manage-limit-orders.md#order-status-lifecycle">order status lifecycle</a>.</td></tr><tr><td><code>createdAt</code></td><td><code>ISO 8601 string</code></td><td>When the order was created.</td></tr></tbody></table>

{% hint style="warning" %}
**One shot.** Submit works only while the order is `PENDING`, so call `/build` and `/submit` back-to-back.
{% endhint %}

#### Submit errors

Only `502` is worth retrying; the 4xx errors are client-side.

<table><thead><tr><th width="80">Status</th><th width="270">Error code</th><th>Scenario</th></tr></thead><tbody><tr><td>451</td><td><code>limitOrderMakerBlacklisted</code></td><td>The orderbook blocks this maker address — an upstream compliance decision, not SwapKit's screening. Permanent for the address.</td></tr><tr><td>400</td><td><code>limitOrderInsufficientAllowance</code></td><td>Allowance too low for the limit-order router. Rebuild, broadcast the returned <code>approvalTx</code>, then submit again.</td></tr><tr><td>400</td><td><code>limitOrderMaxOrdersExceeded</code></td><td>The maker is at the orderbook's open-order cap (1inch: 100). Cancel one first. The message gives the cap.</td></tr><tr><td>409</td><td><code>limitOrderInvalidState</code></td><td>The order is past <code>PENDING</code> or expired, or a <code>signature</code> was sent for a deposit order. On Harbor and NEAR Intents the deposit may already have advanced it: read the order, it's live.</td></tr><tr><td>404</td><td><code>limitOrderNotFound</code></td><td>Unknown <code>orderId</code>.</td></tr><tr><td>401</td><td><code>unauthorized</code></td><td>The order belongs to another API key.</td></tr><tr><td>400</td><td><code>validation_error</code></td><td>No <code>signature</code> or <code>depositTxHash</code>, or an empty one.</td></tr><tr><td>400</td><td><code>limitOrderRejected</code></td><td>Any other orderbook rejection — bad signature, expired, insufficient balance. The message gives the reason.</td></tr><tr><td>502</td><td><code>limitOrderSubmissionFailed</code></td><td>The orderbook failed upstream (5xx or transport). Retry.</td></tr></tbody></table>
