开云体育

I have only limited hands-on experience with the Client Portal API (it does not yet add anything that we can't do via TWS API already), but I think you have mixed up a couple things. If you have not done so yet, take a look at the and the explorer.

Any request you send to a URL that starts with "https://localhost:5000/" is handled by the Client Portal API Java gateway that ships with the Client Portal API installation. The gateway handles two kinds of requests:

• REST requests through one of several API endpoints. All endpoint URLs start with "https://localhost:5000/v1/api/"

• Requests for WebApps that you develop and install in the folder "root/webapps". URLs for WebApps start with "https://localhost:5000" followed by the WebApp name. The gateway simply serves those files to your browser.

The API ships with one WebApp called "demo". It consists of two files and is, consequently, installed under "root/webapps/demo"

• root/webapps/demo/index.html

• root/webapps/demo/gateway.demo.js

The message you get indicates that the gateway is ready to server the WebApp "demo". You start it by pointing your browser to "https://localhost:5000/demo", but the gateway has to be logged into an IBKR account for it to work. In case you have a funded live account at IBKR, you can create a companion "paper" account to try out your strategies.

I do not think that it is possible to connect a WebApp through the Client Portal API gateway to what the TWS application calls a "demo" account. The kind off account you can reach through the TWS application login screen where it says "No username? Try the demo".

Hope that helps,

闯ü谤驳别苍