REDI C# API

newuser

I tried out sample codes and the "monitor orders" and "monitor positions" examples worked fine.

However, C#
Portfolio Trader List Load in C# failed.

The following call returns false with err=NULL

success = ptOrder.Submit(ref err);

Here's the input file I am using.

CSCO,Buy,1,45.9
XLP,Buy,100,
XLU,Sell,100,
XLE,Buy,200,

I am using userid r152885. Perhaps I am not permissioned?

Additionally, is there an example code that shows how to create 'child' orders from these tickets?

Find more posts tagged with

order

redi-api

portfolio-trader

Accepted answers

Christiaan Meihsl

@39783854-26aa-4fea-bc93-00b2ec21f8bb_deprecated_3a75f99c-5134-4b2b-ba84-37662f80bc56,

your input file has the correct format, that is not the issue.

Do you get (for each refused order) a popup similar to this one:

If yes, I suspect there is a permissioning issue with your account. I therefore suggest you contact your Refinitiv account manager. Please post back to tell us if he solved your issue, or if we must continue to investigate.

All comments

Christiaan Meihsl

@39783854-26aa-4fea-bc93-00b2ec21f8bb_deprecated_3a75f99c-5134-4b2b-ba84-37662f80bc56,

your input file has the correct format, that is not the issue.

Do you get (for each refused order) a popup similar to this one:

newuser

No popup but I contacted my account rep for possible permissioning issue.

Christiaan Meihsl

@39783854-26aa-4fea-bc93-00b2ec21f8bb_deprecated_3a75f99c-5134-4b2b-ba84-37662f80bc56,

I tried to investigate further. Today I ran tests twice with the same code and with your instruments:

Around 11am GMT I reproduced your issue (with popups as I described).
Around 4pm GMT the orders were accepted without issue, and I can see them in the Portfolio Trader GUI.

All your instruments are on the US market, I'm wondering if that plays a role. If I am not mistaken US orders should be accepted at 4am ET (9am GMT), maybe even earlier.

I'm investigating in parallel, but if you could try again while the US market is open that could maybe help us pinpoint the cause of the issue.

Also: are you running the latest REDI version ? Between my 2 tests today I upgraded to the latest version 18.2.0.035, that might also have an influence.

EXPLORE OUR SITES