| API Support » Direct-Access API Nov 10, 2008 @ 05:34 PM (Total replies: 4) | |||||
|
Would OEC consider making the API server protocol available to a Unix developer, if he signed an NDA (non-disclosure agreement)? I would assign my intellectual property rights over to OEC, if need be, as I'm not interested in marketing it. |
|||||
| API Support » Direct-Access API Nov 10, 2008 @ 04:53 PM (Total replies: 4) | |||||
|
Can someone please answer the following question: Are there specs available for a direct-access API? I'm referring to the protocol that the API server talks... so that I can write a custom API for my Unix-based trade management system. All that I've seen so far involves the use of "middleware" on a Windows PC... via .NET 2.0 calls, a DLL, or a COM library. This "middleware" eventually has to talk to the API server itself. It's the API server protocol spec I'm looking for. I know it must exist, because one of the Open E Cry pages said this... "A direct connection fee of $0.15 per side will be applied to all commission rates (listed above) for trades sent directly through the OEC API not utilizing the OEC Trader Software." In case this is not yet clear - I only need order entry/execution/updates... no client data (account balance, etc) or data feed of any type. I just want to be able to code to the api.openecry.com server specs so that my Unix trading system can execute orders. Normally I'd do this using FIX, but I understand Open E Cry has an "open" API. Where is it (other than one implemented in Windows-based middleware)? Can someone point me in the right direction, please? Thank you in advance. |
|||||