Brokers with API | Page 3 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Brokers api usage, policy 1 reply

ECN brokers with API that also accepts funds as low as $10000 6 replies

Brokers with free Trading API's? 3 replies

Internet brokers offering api's for automated trading 2 replies

Brokers with API 1 reply

Brokers with API

  • #41
  • Apr 5, 2009 8:57am Apr 5, 2009 8:57am
Quoting paul.stanton
thanks for the detailed list 4xCoder

i'm attempting to use the oanda java api currently, but find the it and support for the product quite lacking.

oanda are the preferred agent because of the tight spread they offer, but with stability obviously a major consideration, i'm considering jumping ship - can anyone recommend another platform?

i basically need reliable rate notifications and order execution with as tight a spread as is available.

regards, paul.
Whats wrong with their java-API? I'm using the .NET version and find it to be quite reliable. The only thing i dont like are 3-second polled quotes(means less updates than on FxTrade), but i understand that java version doesn't have this limitation.
  • #42
  • Apr 5, 2009 2:21pm Apr 5, 2009 2:21pm
i've been given two versions of the java api, one from late 2008, one (which i assume is in alpha phase) from last month.

two main problems with the older java api:
1. At 20:06 (ish) GMT every day I start receiving bogus "Refreshing transactions..." messages and they don't stop until I restart the program.
2. Pretty much every exception is a SessionDisconnectExcetion, meaning that if anything goes wrong (eg trade takes a while to go in, spread has moved, stop is invalid - SessionDisconnect!)
3. There is a consecutive login limit of 40.
4. Without doing a 'logout' a session is not released. ie if you are disconnected, and re-log in you use a new session.
5. problem 2 + problem 3 + problem 4 + a patchy network = total lockout for some period of time.
6. if you login with the same client object after being disconnected, a deadlock occurs.

I am trying to use one client for only rate notifications, one client for only transaction event notifications and one or more clients for placing orders.

I didn't test in depth with the newer API (seems to use soap and load a library from the net at each login) because I ran into a problem early on: as soon as I'd connected two clients simultaneously I'd get a ClassCastException because they would load 2 versions of the same jar (one at each login) meaning you couldn't cast a class to it's own type.
  • #43
  • Last Post: Apr 5, 2009 3:01pm Apr 5, 2009 3:01pm
Yes i find the design that every exception disconnects you also flawed. Its completely unnecessary. For me, this happens most often when an order causes a boundary violation. Something completely normal and expected, but still the client gets disconnected.

I have also one client for rates and all incoming messages and one for sending orders, and a background thread that watches connection states. This way at least i don't loose any incoming messages. I did not run into your other problems, but then again i don't run my app 24/7.
0 traders viewing now