Guides
Guides
Start typing to search…

Order status

Track Order status with InvestGlass and third party OMS or core banking.

General info
InvestGlass OW trading API allows InvestGlass clients to place, check and cancel bulk orders of their end clients.

Authentication

The service uses an OAuth2 token to validate the professional clients using their authorisation token. All requests done to the service must pass the first check.

Security Scheme > HTTP

Header Bearer

Value ALPHANUMERIC

Required Yes

Description The authorisation token

InvestGlass provides a Postman library to connect to its REST API. You can download it.

Product universe

Equity
ETF Funds Bonds Options and Futures Digital assets

For all asset class please get in touch with InvestGlass team.

Instrument needs to be tradable online; for more information about our product universe, please check help.investglass.com

Guidelines for securities

Please find below some guidelines for using the InvestGlass - OMS trading API for securities trading:

  1. when placing an order, the parameter "best effort" is used if the user wants execution to be independent across accounts (i.e. during an order containing three accounts, one account gets rejected, and the execution will continue the two remaining accounts). The default value is false
  2. when placing an order, the "dry run" parameter allows the user to proceed with technical and business tests without executing the order on the specified exchange. The default value is false
  3. when placing an order, to correctly identify an instrument, the user can:
    1. option 1:
      provide financial instrument details with the ISIN of the instrument provide a place of trade with the right MIC provide currency with the currency of the instrument
    2. option 2:
      provide financialInstrumentDetails with the stockKey (i.e. ISIN_MIC number_Currency)
    3. option 3, options and futures:
      provide underlying symbol, option type, option style, StrikePrice, MaturityDate, Multiplier
    4. order can only be executed with the following characteristics:
      1. executionType:
      2. market
      3. limit
      4. stop
      5. stopLimit
      6. timeInForce:
      7. goodTillDate

Guidelines for digital assets
Please find below some guidelines to use the OW trading API for crypto currencies trading:

  1. placing an order on a digital asset can be processed only on one your PMS OMS account
    bulkOrderDetails.numberOfAllocations should be equal to 1 requestedAllocationList should have only 1 element
  2. when placing an order, the parameter "dryRun" allows the user to proceed technical and business test without execution of the order on the specified exchange. Default value is false
  3. when placing an order, to correctly identify a digital asset, the user must:
    1. input the financialInstrumentIdentification object like:
      1. identification equal to "Crypto: <crypto_symbol>" (with crypto_symbol could be BTC, ETH, ...)
      2. type equal to "otherProprietaryIdentification
        provide the currency such that:
      3. bulkOrderDetails.currency should be the quote currency of the pair (e.g. in BTC/USD it is USD)
      4. bulkOrderDetails.cashAccountCurrency should be null
      5. order can only be executed with the following characteristics:
      6. executionType:
        1. limit
        2. stopLimit
        3. timeInForce:
        4. goodTillCancel
        5. immediateOrCancel
        6. fillOrKill
        7. Production instance data

Production Instance data

The Production instance supports all the universe of securities available to InvestGlass clients.


Sandbox data
The sandbox supports following products currently:

List of supported products
InvestGlass exchange id to MIC mapping:

List of stock exchange code mappings

Sandbox Order execution logic

In the demo environment, all orders are processed against a simulator that will simulate the stock exchange. It uses the total quantity in order to decide the scenario it will play. The simulator uses volatile storage, so it is not guaranteed that orders are persisted across more than several hours

Scenarios:

Quantity Behaviour on new order

2.**** Order placed

3.**** Order placed, then partial fill of 1 unit (or 10 000)

4.**** Order placed, then full fill of the order

5.**** Order placed, then 3 partial fills of 1/5 of the order (or 10 000) then full fill

82.**** Order rejected