I'm on standby waiting for tech support to respond so I'm posting here. The reason I'm posting here, of course, is because trading day time is limited for software development since they have no test servers. I want other developers to save time and possibly look at this later for reference. (Or, you know, they can assist me. That being said, I think there is a bug in their library. Their protocol document online says that the client library is supposed to send: 0x0002, 0x0008, 0x0111, 0x0101, 0x0000, 0x0000 These are all 16-bit quantities transmitted in little-endian order. However, when you actually inspect the wire, the GTAPIB library is actually sending: 0x0002, 0x0008, 0x0110, 0x0101, 0x0000, 0x0000 So either their documentation is broken, or their library is broken. The server then eventually disconnects me. Its second response calls the 'connect event' callback to be called and that's it. Are there more issues with the library, and am I wasting my time? I get the feeling GTAPIB is not used very often and is very neglected. Is someone else out there using one of their other APIs with greater success? Fortunately, I only intend to use this API for reading data and not placing orders. I'm wondering, however, if there are bugs in their order placement code and whether or not that even works as advertised.