Yes. The Customer Indicator field lets you add a string value on the order (e.g. tag each order with "Strategy ABC").
Once the order is submitted, you can view the value in the "Client Data Field" field in the Message Monitor.
No (the Allocation window itself in REDI must be used to allocate).
You can, however, specify an account on each order, which facilitates pre-trade allocations.
Once an order is placed using the API, users can allocate using the REDI Allocation window.
(but orders sent through the API get sent through the risk management service to be checked)
Yes, please see the Tutorials section.
You can upload lists (tickets, not orders) to REDI PT, but you cannot send orders to PT.
Yes. Please check out REDI API tutorials for more.
Yes. Please check out Spread Trader API Specification in the Documents tab for more.
An account represents a grouping of trade activity. (e.g. buy 100 shares of TRI in account EQUITIES123)
While it's a required field for order entry, not all clients necessarily use it the same way. (e.g. some clients pre-trade allocate into an account, some clients populate it with a "top account" , some clients populate a dummy value (e.g. "TEST" just to send an order, etc).
In FIX, the account field is usually the value sent in tag 1 to the broker. (but can be other tags as well, depending on broker/client/etc)
It could be related to a few things, but in most cases, you may be missing an entitlement that enables you to use the API. Please reach out to your account manager to get set up.
REDI.ORDER: Used to send equities and futures orders
REDI.OPTIONORDER: Used to send options orders
REDI.SPREAD: Used to create spreads (e.g. pairs trading)
REDI.TICKET: Used to create tickets (i.e. parent orders)
REDI.QUERY: Used to obtain order information (e.g. order status)
REDI.DONEAWAY: Doneaways are manual trade notifications (e.g. enter a doneaway to alert REDI of a trade done outside of REDI)
REDI.TFLIST: Lists, or baskets, represent groups of tickets. These can be sent to brokers in batches, or waves, using the REDI Portfolio Trader.
Performance can vary based on hardware specs, order type, and more, but in general, expect to see ~3 orders/second supported in the REDI API. Submit2 will be slightly faster.
Some actions, such as Portfolio Trader imports, can take longer.
We also offer a higher throghput solution using our FIX API - please reach out to your account manager for more details.
Please see this link for the complete list of the available destinations.
When Symbol is selected in REDIPlus desktop's Montage, then the dropdown list of available REDI destinations becomes available .
These are the destinations to use in code.
Missing reference could result in this error. To verify, from Menu select
Developer-> Vew Code
If the reference is missing:
Add it by selecting:
View all files to select "REDIAddIn.xla".
And reference should change to valid.