Edit Limit Order (PATCH)

Edit Limit Order

This API is used to edit a limit order task

URL

Header: X-API-KEY

(Please do not disclose your API Key to anyone. If you are at risk of losing it, please refresh it.)

Notes

  1. X-API-KEY can be obtained in your "Dashboard", go to check: Dashboard

  2. In the paging type interface, use the next field in the return value as the query parameter for the next page (if next == null, it means that paging has ended)

Request Example

{
	"id": "lmn27zhq065q3u",
	"enabled": true,
	"groupId": "m53gevri055ird",
	"triggerPriceUsd": "1.5",
	"triggerDirection": "up",
	"priorityFee": "0.00005",
	"currencyAmountUI": 1,
	"gasFeeDelta": 5,
	"maxFeePerGas": 100,
	"jitoEnabled": true,
	"jitoTip": 0.001,
	"expireDelta": 360000000,
	"expireExecute": false,
	"maxSlippage": 0.1,
	"concurrentNodes": 2,
	"retries": 1
}

Request Response

{
	"err": false,
	"res": "",
	"docs": "https://dbotx.com/docs"
}

Request Parameters

  • id: Limit order task id

  • enabled: Task enable status, true/false

  • groupId: Group id

  • triggerPriceUsd: Price (USD) that triggers buy / sell

  • triggerDirection: "down" means buy/sell below the trigger price, "up" means buy/sell above the trigger price

  • currencyAmountUI: When trade type is buy, fill in the buy amount (ETH/SOL/BNB/TRX), when tradeType is sell, fill in the sell ratio (0-1)

  • priorityFee: Priority Fee (SOL), valid for Solana, empty string means use auto priority fee

  • gasFeeDelta: Extra added gas (Gwei), valid for EVM

  • maxFeePerGas: When the base gas exceeds this value, no transaction will execute (Gwei), valid for EVM chains

  • jitoEnabled: "true" means enable anti-MEV mode (Solana & Ethereum)

  • jitoTip: Bribery tip used by Anti-MEV (Solana)

  • expireDelta: Task duration, max 864000000 (milliseconds)

  • expireExecute: “true” means that when a task expires and is not triggered, the token will be bought or sold at the real-time price at that time

  • maxSlippage: MAX slippage tolerance (0.00-1.00)

  • concurrentNodes: Number of concurrent nodes (1-3)

  • retries: Number of retries after failure (0-10)

Last updated