NDAX OMS Orders API

The OMS Orders API from NDAX — 15 operation(s) for oms orders.

Operations 15

POST /CancelAllOrders Cancel All Orders #
POST /CancelOrder Cancel Order #
POST /CancelQuote Cancel Quote #
POST /CancelReplaceOrder Cancel Replace Order #
POST /CreateQuote Create Quote #
POST /GetOpenOrders Get Open Orders #
POST /GetOpenQuotes Get Open Quotes #
POST /GetOrderFee Get Order Fee #
POST /GetOrderHistory Get Order History #
POST /GetOrderHistoryByOrderId Get Order History By Order Id #
POST /GetOrdersHistory Get Orders History #
POST /GetOrderStatus Get Order Status #
POST /ModifyOrder Modify Order #
POST /SendOrder Send Order #
POST /UpdateQuote Update Quote #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/ndax:ndax-oms-orders-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

ndax-oms-orders-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Ndax Pro OMS Orders API
  version: '2026-10-13'
  description: 'Generated by API Evangelist from the Ndax Pro API reference at https://apidoc.ndax.io (Slate). Ndax is built on AlphaPoint: every function is documented as a JSON payload sent inside a message frame {m,i,n,o} over wss://api.ndax.io/WSGateway/. Public functions also answer over HTTP at https://api.ndax.io:8443/AP/{FunctionName} (Ping, GetInstruments and GetProducts verified live 2026-10-13). Each path here is a documented function name; this is NOT a provider-published contract.'
  contact:
    url: https://ndax.io/support
  termsOfService: https://ndax.io/en/legal/account-agreements
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-13'
  x-generator: deterministic parse of https://apidoc.ndax.io section headings, Category/Permissions/CallType lines and request/response examples (no model)
servers:
- url: https://api.ndax.io:8443/AP
  description: Ndax AlphaPoint HTTP gateway
security:
- apiKeySignature: []
tags:
- name: OMS Orders
paths:
  /CancelAllOrders:
    post:
      operationId: cancelAllOrders
      summary: Cancel All Orders
      description: 'Cancels all open matching orders for the specified account on an Order Management System. A user with Trading permission can cancel orders for himselfd; a user with Operator permissions can cancel orders for any account, instrument, or user. Note: Multiple users may have access to the same account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#cancelallorders
      x-websocket-function: CancelAllOrders
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
                result: true
                errormsg: ''
                errorcode: 0
                detail: ''
      x-requires-session: true
  /CancelOrder:
    post:
      operationId: cancelOrder
      summary: Cancel Order
      description: Cancels an open order that has been placed but has not yet been fully executed. A user with Trading permission can cancel an order only for an account with which he is associated; a user with Operator permission can cancel an order for any account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#cancelorder
      x-websocket-function: CancelOrder
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /CancelQuote:
    post:
      operationId: cancelQuote
      summary: Cancel Quote
      description: 'Cancels a quote that has not been executed yet. Note: Quoting is not enabled for the retail end user of the AlphaPoint software. Only registered market participants or marketmakers may quote. Only a user with Operator permission can cancel quotes for another user. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Marketmaker
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#cancelquote
      x-websocket-function: CancelQuote
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              omsId: 0
              accountId: 0
              instrumentId: 0
              bidQuoteId: 0
              askQuoteId: 0
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /CancelReplaceOrder:
    post:
      operationId: cancelReplaceOrder
      summary: Cancel Replace Order
      description: 'CancelReplaceOrder is a single API call that both cancels an existing order and replaces it with a new order. Canceling one order and replacing it with another also cancels the order’s priority in the order book. You can use ModifyOrder to preserve priority in the book; but ModifyOrder only allows a reduction in order quantity. Warning: CancelReplaceOrder sacrifices the order''s priority in the order book. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#cancelreplaceorder
      x-websocket-function: CancelReplaceOrder
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              omsId: 0
              orderIdToReplace: 0
              clientOrdId: 0
              orderType: 0
              side: 0
              accountId: 0
              instrumentId: 0
              useDisplayQuantity: false
              displayQuantity: 0.0
              limitPrice: 0.0
              stopPrice: 0.0
              referencePrice: 0.0
              pegPriceType: 0
              timeInForce: 0
              orderIdOCO: 0
              quantity: 0.0
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /CreateQuote:
    post:
      operationId: createQuote
      summary: Create Quote
      description: 'TK call and response may change Creates a quote. A quote expresses a willingness to buy or sell at a given price. Both a quote and an order will execute. Only a user with Operator or MarketMaker permission can create a quote. Note: Quoting is not enabled for the retail end user of AlphaPoint software. Only registered market participants or market makers may quote. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, MarketMaker
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#createquote
      x-websocket-function: CreateQuote
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /GetOpenOrders:
    post:
      operationId: getOpenOrders
      summary: Get Open Orders
      description: Returns an array of 0 or more orders that have not yet been filled (open orders) for a single account on a specific Order Management System. The call returns an empty array if an account has no open orders. A user with Trading or AccountReadOnly permission must be associated with the account named by AccountId; a user with Operator permissoin can get open orders for any account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading, AccountReadOnly
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getopenorders
      x-websocket-function: GetOpenOrders
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
              - Side: Buy
                OrderId: 0
                Price: 0.0
                Quantity: 0.0
                DisplayQuantity: 0.0
                Instrument: 0
                Account: 0
                OrderType: Unknown
                ClientOrderId: 0
                OrderState: Unknown
                ReceiveTime: 0
                ReceiveTimeTicks: 0
                OrigQuantity: 0.0
                QuantityExecuted: 0.0
                AvgPrice: 0.0
                CounterPartyId: 0
                ChangeReason: Unknown
                OrigOrderId: 0
                OrigClOrdId: 0
                EnteredBy: 0
                IsQuote: false
                InsideAsk: 0.0
                InsideAskSize: 0.0
                InsideBid: 0.0
                InsideBidSize: 0.0
                LastTradePrice: 0.0
                RejectReason: ''
                IsLockedIn: false
                CancelReason: ''
                OMSId: 0
      x-requires-session: true
  /GetOpenQuotes:
    post:
      operationId: getOpenQuotes
      summary: Get Open Quotes
      description: Returns the current bid and ask quotes for a given instrument ID and account ID. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, MarketMaker
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getopenquotes
      x-websocket-function: GetOpenQuotes
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
                bid:
                  omsId: 0
                  side: 0
                  orderId: 0
                  price: 0.0
                  quantity: 0.0
                  displayQuantity: 0.0
                  instrument: 0
                  account: 0
                  orderType: 0
                  clientOrderId: 0
                  orderState: 0
                ask:
                  omsId: 0
                  side: 0
                  orderId: 0
                  price: 0.0
                  quantity: 0.0
                  displayQuantity: 0.0
                  instrument: 0
                  account: 0
                  orderType: 0
                  clientOrderId: 0
                  orderState: 0
      x-requires-session: true
  /GetOrderFee:
    post:
      operationId: getOrderFee
      summary: Get Order Fee
      description: Returns an estimate of the transaction fee for a specific order side, instrument, and order type. Fees are set and calculated by the operator of the trading venue. The exchange generally deducts fees from the "receiving" side of the trade (although an operator can modify this). There are two products in every trade (and in every instrument); for example, the instrument BTCUSD comprises a BitCoin product and a US dollar product. Placing a buy order on the book causes fees to be deducted from Product 1, in this case, BitCoin; placing a sell order causes fees to be deducted from Product 2, in thi Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getorderfee
      x-websocket-function: GetOrderFee
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              omsId: 0
              accountId: 0
              instrumentId: 0
              productId: 0
              amount: 0.0
              price: 0.0
              orderType: 0
              makerTaker: 0
              side: 0
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /GetOrderHistory:
    post:
      operationId: getOrderHistory
      summary: Get Order History
      description: Returns a complete list of all orders, both open and executed, for a specific account on the specified Order Management System. The account named in the request must be associated with the calling user. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Trading, AccountReadOnly
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getorderhistory
      x-websocket-function: GetOrderHistory
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
              - Side: Buy
                OrderId: 0
                Price: 0.0
                Quantity: 0.0
                DisplayQuantity: 0.0
                Instrument: 0
                Account: 0
                OrderType: Unknown
                ClientOrderId: 0
                OrderState: Unknown
                ReceiveTime: 0
                ReceiveTimeTicks: 0
                OrigQuantity: 0.0
                QuantityExecuted: 0.0
                AvgPrice: 0.0
                CounterPartyId: 0
                ChangeReason: Unknown
                OrigOrderId: 0
                OrigClOrdId: 0
                EnteredBy: 0
                IsQuote: false
                InsideAsk: 0.0
                InsideAskSize: 0.0
                InsideBid: 0.0
                InsideBidSize: 0.0
                LastTradePrice: 0.0
                RejectReason: ''
                IsLockedIn: false
                CancelReason: ''
                OMSId: 0
      x-requires-session: true
  /GetOrderHistoryByOrderId:
    post:
      operationId: getOrderHistoryByOrderId
      summary: Get Order History By Order Id
      description: Retrieves the full order history of a specific order by its order ID, including any changes. A user with Trading permission can retrieve an order history only for the user's accounts and instruments; a user with Operator permission can retrieve all accounts and instruments. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getorderhistorybyorderid
      x-websocket-function: GetOrderHistoryByOrderId
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              omsId: 0
              orderId: 0
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
              - Side: Buy
                OrderId: 0
                Price: 0.0
                Quantity: 0.0
                DisplayQuantity: 0.0
                Instrument: 0
                Account: 0
                OrderType: Unknown
                ClientOrderId: 0
                OrderState: Unknown
                ReceiveTime: 0
                ReceiveTimeTicks: 0
                OrigQuantity: 0.0
                QuantityExecuted: 0.0
                AvgPrice: 0.0
                CounterPartyId: 0
                ChangeReason: Unknown
                OrigOrderId: 0
                OrigClOrdId: 0
                EnteredBy: 0
                IsQuote: false
                InsideAsk: 0.0
                InsideAskSize: 0.0
                InsideBid: 0.0
                InsideBidSize: 0.0
                LastTradePrice: 0.0
                RejectReason: ''
                IsLockedIn: false
                CancelReason: ''
                OMSId: 0
      x-requires-session: true
  /GetOrdersHistory:
    post:
      operationId: getOrdersHistory
      summary: Get Orders History
      description: Retrieves an array of multiple orders (hence, GetOrdersHistory with plural Orders ) for the specified account, order ID, user, instrument, or time stamp. The history starts at index i , where i is an integer identifying a specific order (the most recent order has an index of 0). “Depth” is the count of trades to report backwards from startIndex . All values in the call other than OMSId are optional. For example, if depth = 200 and startIndex = 0, the history returns 200 orders into the past starting with the most recent (0) order. If depth = 200 and startIndex = 100, the history returns 200 or Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getordershistory
      x-websocket-function: GetOrdersHistory
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              omsId: 0
              accountId: 0
              clientOrderId: 0
              originalOrderId: 0
              originalClientOrderId: 0
              userId: 0
              instrumentId: 0
              startTimestamp: 0
              endTimestamp: 0
              depth: 100
              startIndex: 0
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
              - Side: Buy
                OrderId: 0
                Price: 0.0
                Quantity: 0.0
                DisplayQuantity: 0.0
                Instrument: 0
                Account: 0
                OrderType: Unknown
                ClientOrderId: 0
                OrderState: Unknown
                ReceiveTime: 0
                ReceiveTimeTicks: 0
                OrigQuantity: 0.0
                QuantityExecuted: 0.0
                AvgPrice: 0.0
                CounterPartyId: 0
                ChangeReason: Unknown
                OrigOrderId: 0
                OrigClOrdId: 0
                EnteredBy: 0
                IsQuote: false
                InsideAsk: 0.0
                InsideAskSize: 0.0
                InsideBid: 0.0
                InsideBidSize: 0.0
                LastTradePrice: 0.0
                RejectReason: ''
                IsLockedIn: false
                CancelReason: ''
                OMSId: 0
      x-requires-session: true
  /GetOrderStatus:
    post:
      operationId: getOrderStatus
      summary: Get Order Status
      description: Retrieves the status information for a single order. A user with Trading permission can retrieve status information for accounts and orders with which the user is associated; a user with Operator permission can retreive status information for any account or order ID. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#getorderstatus
      x-websocket-function: GetOrderStatus
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
              example:
              - Side: Buy
                OrderId: 0
                Price: 0.0
                Quantity: 0.0
                DisplayQuantity: 0.0
                Instrument: 0
                Account: 0
                OrderType: Unknown
                ClientOrderId: 0
                OrderState: Unknown
                ReceiveTime: 0
                ReceiveTimeTicks: 0
                OrigQuantity: 0.0
                QuantityExecuted: 0.0
                AvgPrice: 0.0
                CounterPartyId: 0
                ChangeReason: Unknown
                OrigOrderId: 0
                OrigClOrdId: 0
                EnteredBy: 0
                IsQuote: false
                InsideAsk: 0.0
                InsideAskSize: 0.0
                InsideBid: 0.0
                InsideBidSize: 0.0
                LastTradePrice: 0.0
                RejectReason: ''
                IsLockedIn: false
                CancelReason: ''
                OMSId: 0
      x-requires-session: true
  /ModifyOrder:
    post:
      operationId: modifyOrder
      summary: Modify Order
      description: 'Reduces an order’s quantity without losing priority in the order book. An order’s quantity can only be reduced. The other call that can modify an order — CancelReplaceOrder — resets order book priority, but you can use it to increase an order. Note: ModifyOrder does not surrender or reset order book priority. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#modifyorder
      x-websocket-function: ModifyOrder
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /SendOrder:
    post:
      operationId: sendOrder
      summary: Send Order
      description: 'Creates an order. Anyone submitting an order should also subscribe to the various market data and event feeds, or call GeOpenOrders or GetOrderStatus to monitor the status of the order. If the order is not in a state to be executed, GetOpenOrders will not return it. A user with Trading permission can create an order only for those accounts and instruments with which the user is associated; a user with Operator permissions can create an order for any account and instrument. Note: Call Type is asynchronous. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, Trading
      x-call-type: Asynchronous
      x-docs-url: https://apidoc.ndax.io/#sendorder
      x-websocket-function: SendOrder
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              InstrumentId: 1
              OMSId: 1
              AccountId: 1
              TimeInForce: 1
              ClientOrderId: 1
              OrderIdOCO: 0
              UseDisplayQuantity: false
              Side: 0
              quantity: 1
              OrderType: 2
              PegPriceType: 3
              LimitPrice: 8800
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
  /UpdateQuote:
    post:
      operationId: updateQuote
      summary: Update Quote
      description: Updates an existing quote. Quoting is not enabled for the retail end user of the AlphaPoint software. Only registered market participants or market makers may quote. Warning **UpdateQuote** resets the quote's priority in the order book. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
      tags:
      - OMS Orders
      x-category: User
      x-permissions: Operator, MarketMaker
      x-call-type: Synchronous
      x-docs-url: https://apidoc.ndax.io/#updatequote
      x-websocket-function: UpdateQuote
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
            example:
              OMSId: 0
              AccountId: 0
              InstrumentId: 0
              BidQuoteId: 0
              Bid: 0
              BidQTY: 0
              AskQuoteId: 0
              Ask: 0
              AskQTY: 0
      responses:
        '200':
          description: Function reply payload.
          content:
            application/json:
              schema: {}
      x-requires-session: true
components:
  securitySchemes:
    apiKeySignature:
      type: apiKey
      in: header
      name: Authorization
      x-source: https://apidoc.ndax.io/#authenticateuser