tradingOrdersDocsPage.orderManagement
Order Placement and Management APIs
Create, close, cancel, and update orders through authenticated Finger Trader trading endpoints.
Order write endpoints
These endpoints can submit or change live orders. Confirm the account, market, instrument, quantity, and broker-specific rules before trying a request.
POST request with Bearer Access Token and a JSON body. The Flutter client uses the authenticated Finger Trader app BFF base URL. Getting Started: authentication
https://prod-api.fingertrader.com/finger-bff-appAuthorization headerAuthorization: Bearer <ACCESS_TOKEN>Requires an activated Finger Trader account and an account opened with a broker in the Finger ecosystem. Use the Bearer Access Token described in Getting Started.
Successful responses use the standard Finger Trader envelope: code, data, and msg. See each response example for the data shape parsed by the Flutter client.
Create order
POST /app-api/v1/order/create-order
Submits a new order request.
Request example
Illustrative values only. Replace the ticker, market, user/order identifiers, and broker identifiers with values returned for your own account. Verify each field with your broker before sending.
{
"ticker": "EURUSD",
"orderType": 1,
"orderSide": 1,
"qty": "1000",
"coinType": 0,
"walletType": 2,
"price": "1.08500",
"marginRate": 10,
"stopLoss": "1.07500",
"takeProfit": "1.09500",
"marketType": 0
}| Parameter | Type | DTO presence | Reference |
|---|---|---|---|
ticker | string | Nullable | Broker-supported tickers and symbols |
orderType | integer | Nullable | Trading enum values |
orderSide | integer | Nullable | Trading enum values |
qty | decimal string | Nullable | — |
coinType | integer | Nullable | Trading enum values |
walletType | integer | Nullable | Trading enum values |
price | decimal string | Nullable | — |
marginRate | integer | Nullable | — |
stopLoss | decimal string | Nullable | — |
takeProfit | decimal string | Nullable | — |
marketType | integer | Nullable | Market support and marketType codes |
brokerId | integer | Nullable | — |
Nullable in the Flutter DTO means the client can encode null or omit some optional IDs; it does not confirm server-side validation rules. Confirm required fields with your broker/service.
Response example
{"code":0,"data":true,"msg":""}The client expects data to be a boolean result.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Try a REST request · /app-api/v1/order/create-order
Enter your Access Token and edit the request parameters. The browser sends this request directly to the selected official Finger Trader BFF environment.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Ready. Nothing is sent until you select Send request.
The response will appear here.
The Access Token stays in this page memory and is not saved to browser storage or sent to Finger Trader website servers. It is sent only to the selected official API environment after you click Send request. Clear it when finished.
Close order
POST /app-api/v1/order/close-order
Submits a position close request.
Request example
Illustrative values only. Replace the ticker, market, user/order identifiers, and broker identifiers with values returned for your own account. Verify each field with your broker before sending.
{
"userId": "user_demo_12345",
"orderId": "order_demo_20250101_001",
"qty": "500",
"marketType": 0,
"brokerId": 10001,
"brokerPositionId": "position_demo_001",
"symbol": "EURUSD"
}| Parameter | Type | DTO presence | Reference |
|---|---|---|---|
userId | string | Nullable | — |
orderId | string | Nullable | — |
qty | decimal string | Nullable | — |
marketType | integer | Nullable | Market support and marketType codes |
brokerId | integer | Nullable | — |
brokerPositionId | string | Nullable | — |
symbol | string | Nullable | Broker-supported tickers and symbols |
Nullable in the Flutter DTO means the client can encode null or omit some optional IDs; it does not confirm server-side validation rules. Confirm required fields with your broker/service.
Response example
{"code":0,"data":true,"msg":""}The client expects data to be a boolean result.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Try a REST request · /app-api/v1/order/close-order
Enter your Access Token and edit the request parameters. The browser sends this request directly to the selected official Finger Trader BFF environment.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Ready. Nothing is sent until you select Send request.
The response will appear here.
The Access Token stays in this page memory and is not saved to browser storage or sent to Finger Trader website servers. It is sent only to the selected official API environment after you click Send request. Clear it when finished.
Cancel limit order
POST /app-api/v1/order/cancel-order
Submits a limit-order cancel request.
Request example
Illustrative values only. Replace the ticker, market, user/order identifiers, and broker identifiers with values returned for your own account. Verify each field with your broker before sending.
{
"userId": "user_demo_12345",
"orderId": "order_demo_20250101_002",
"marketType": 0,
"brokerId": 10001,
"brokerOrderId": "broker_order_demo_002",
"clientOrderId": "client_order_demo_002"
}| Parameter | Type | DTO presence | Reference |
|---|---|---|---|
userId | string | Nullable | — |
orderId | string | Nullable | — |
marketType | integer | Nullable | Market support and marketType codes |
brokerId | integer | Nullable | — |
brokerOrderId | string | Nullable | — |
clientOrderId | string | Nullable | — |
Nullable in the Flutter DTO means the client can encode null or omit some optional IDs; it does not confirm server-side validation rules. Confirm required fields with your broker/service.
Response example
{"code":0,"data":true,"msg":""}The client expects data to be a boolean result.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Try a REST request · /app-api/v1/order/cancel-order
Enter your Access Token and edit the request parameters. The browser sends this request directly to the selected official Finger Trader BFF environment.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Ready. Nothing is sent until you select Send request.
The response will appear here.
The Access Token stays in this page memory and is not saved to browser storage or sent to Finger Trader website servers. It is sent only to the selected official API environment after you click Send request. Clear it when finished.
Modify stop loss / take profit
POST /app-api/v1/order/modify-stop-profit-loss
Submits an order update request for stop loss or take profit.
Request example
Illustrative values only. Replace the ticker, market, user/order identifiers, and broker identifiers with values returned for your own account. Verify each field with your broker before sending.
{
"userId": "user_demo_12345",
"orderId": "order_demo_20250101_003",
"qty": "1000",
"price": "1.08600",
"stopLose": "1.07600",
"stopProfit": "1.09600",
"clearStopLoss": false,
"clearTakeProfit": false
}| Parameter | Type | DTO presence | Reference |
|---|---|---|---|
userId | string | Nullable | — |
orderId | string | Nullable | — |
qty | decimal string | Nullable | — |
price | decimal string | Nullable | — |
stopLose | decimal string | Nullable | — |
stopProfit | decimal string | Nullable | — |
clearStopLoss | boolean | Nullable | — |
clearTakeProfit | boolean | Nullable | — |
Nullable in the Flutter DTO means the client can encode null or omit some optional IDs; it does not confirm server-side validation rules. Confirm required fields with your broker/service.
Response example
{"code":0,"data":true,"msg":""}The client expects data to be a boolean result.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Try a REST request · /app-api/v1/order/modify-stop-profit-loss
Enter your Access Token and edit the request parameters. The browser sends this request directly to the selected official Finger Trader BFF environment.
Try sends a real request to the selected environment and may place, close, cancel, or modify an order. Use a test account and broker-approved test environment where available.
Ready. Nothing is sent until you select Send request.
The response will appear here.
The Access Token stays in this page memory and is not saved to browser storage or sent to Finger Trader website servers. It is sent only to the selected official API environment after you click Send request. Clear it when finished.