FINGER TRADER

brokerageDocsPage.riskControl

Risk Control APIs

Interfaces used by the broker console to inspect market order pools and customer positions, with controls linked to trading configuration.

Documentation framework · Overview

Authentication and access

These interfaces require an authorized broker or merchant staff session and the relevant backend permissions. They are not authenticated by an ordinary end-customer trading-app token. Confirm access with the broker administrator.

Send JSON POST requests to the selected merchant BFF environment. The Finger Admin client sends its signed-in broker-staff access token in the Authorization header as a Bearer token.

https://dev-api.fingertrading.com/finger-bff-merchant
Authorization: Bearer <BROKER_STAFF_ACCESS_TOKEN>

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

Endpoints in this section

Broker-side risk workflows combine customer order and position queries with controls configured under Trading configuration.

Market order pool

Queries the market order pool using MarketQueryDTO.

POST/mer-api/v1/order/market-order-list

Request example

{
  "marketType": 0
}

Request fields

marketTypenumber

Response example

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

{
  "code": 0,
  "data": {
    "total": 1,
    "items": [
      {
        "id": "sample-id",
        "userNumber": "U10001",
        "status": 1
      }
    ]
  },
  "msg": "success"
}
Try this request · /mer-api/v1/order/market-order-list

Ready. The request is not sent until you press Send.

Response
—

The token is held only in this page session and is not saved by this documentation page. Avoid shared devices and clear the token when finished.

Market ticker/order data

Paged market data list; TickerListQueryDTO filters by marketType.

POST/mer-api/v1/order/market-data-list

Request example

{
  "page": 1,
  "pageSize": 20,
  "query": {
    "marketType": 0
  }
}

Request fields

pagenumber
pageSizenumber
queryobject

Response example

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

{
  "code": 0,
  "data": {
    "total": 1,
    "items": [
      {
        "id": "sample-id",
        "userNumber": "U10001",
        "status": 1
      }
    ]
  },
  "msg": "success"
}
Try this request · /mer-api/v1/order/market-data-list

Ready. The request is not sent until you press Send.

Response
—

The token is held only in this page session and is not saved by this documentation page. Avoid shared devices and clear the token when finished.

Customer open positions

Paged customer holdings query.

POST/mer-api/v1/order/get-user-order-holding-list

Request example

{
  "page": 1,
  "pageSize": 20,
  "query": {
    "userNumber": "",
    "brokerNumber": "",
    "marketType": 0,
    "startTime": "",
    "endTime": ""
  }
}

Request fields

pagenumber
pageSizenumber
queryobject

Response example

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

{
  "code": 0,
  "data": {
    "total": 1,
    "items": [
      {
        "id": "sample-id",
        "userNumber": "U10001",
        "status": 1
      }
    ]
  },
  "msg": "success"
}
Try this request · /mer-api/v1/order/get-user-order-holding-list

Ready. The request is not sent until you press Send.

Response
—

The token is held only in this page session and is not saved by this documentation page. Avoid shared devices and clear the token when finished.

Close order

Closes the order identified by IDDTO.

POST/mer-api/v1/order/close-order

Request example

{
  "id": "demo-record-id"
}

Request fields

idstring

Response example

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

{
  "code": 0,
  "data": true,
  "msg": "success"
}
Try this request · /mer-api/v1/order/close-order

This endpoint changes broker data or order state. Try sends a real request; it is not a simulation. Use an approved test account and environment.

Ready. The request is not sent until you press Send.

Response
—

The token is held only in this page session and is not saved by this documentation page. Avoid shared devices and clear the token when finished.

User matching configuration

Reads the matching configuration for a market/user context.

POST/mer-api/v1/trade/user-match-config

Request example

{
  "marketType": 0
}

Request fields

marketTypenumber

Response example

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

{
  "code": 0,
  "data": {
    "id": "sample-id",
    "status": 1
  },
  "msg": "success"
}
Try this request · /mer-api/v1/trade/user-match-config

Ready. The request is not sent until you press Send.

Response
—

The token is held only in this page session and is not saved by this documentation page. Avoid shared devices and clear the token when finished.

Set user matching configuration

Updates the user matching configuration.

POST/mer-api/v1/trade/user-match-config-set

Request example

{
  "marketType": 0,
  "userId": "demo-user-id",
  "value": {
    "status": 1,
    "orderSide": 0,
    "rate": 1,
    "followOrderFirst": false
  }
}

Request fields

marketTypenumber
userIdstring
valueobject

Response example

Examples are illustrative. Replace identifiers with values from your authorized account. Response payload shapes are examples inferred from Finger Admin client usage; confirm the exact contract with your broker. Configuration and order-action requests can change live data.

{
  "code": 0,
  "data": true,
  "msg": "success"
}
Try this request · /mer-api/v1/trade/user-match-config-set

This endpoint changes broker data or order state. Try sends a real request; it is not a simulation. Use an approved test account and environment.

Ready. The request is not sent until you press Send.

Response
—

The token is held only in this page session and is not saved by this documentation page. Avoid shared devices and clear the token when finished.