API Support Forum
User Profile

Viewing User Profile for: CMicciche902



Oct 04, 2019 03:26 PM

Oct 04, 2019 03:26 PM

Post Statistics
CMicciche902 has contributed to 225 posts out of 4461 total posts

20 most recent posts:

API Support » Auto reconnect? Oct 04, 2019 @ 03:26 PM (Total replies: 3)

I've confirmed with our Developers auto-reconnect is a front-end feature in our trading platform, not an API feature. We have a fix for our software, but does not impact API. You'll need to implement your own reconnect feature in your own application.
Chris M

API Support » Auto reconnect? Sep 23, 2019 @ 08:35 AM (Total replies: 3)

Yes, however, there is an issue that will be addressed. This may not necessarily require new build of GF API. Once fixed, I’ll post details in the forum.
Chris M

API Support » Order status change response issue Sep 12, 2019 @ 10:46 AM (Total replies: 1)

You sent two orders, therefore two id's. Comment isn't validated, just a text field for your own purpose. Are you trying to send as OSO or OCO? Review api docs for correct use.

Order #207987426 Buy 0/3 ESU19 STP 3009.50 B-1-SL by BGoyal9136/API003710 TradeStreategy
Did you review rejection reason: Buy order stop price must be above last trade price

Order #207987428 Buy 3/3 ESU19 MKT B-1-SL by BGoyal9136/API003710 TradeStreategy
Chris M

Order Execution » Order state change response Sep 10, 2019 @ 12:16 PM (Total replies: 3)

Sure, plus Stop, Stop Limit, Trailing Stop, etc. GTC is intended for order to work for many sessions where fill is not guaranteed immediate fill.
Chris M

API Support » Can't connect to the FAST price server Sep 10, 2019 @ 11:18 AM (Total replies: 3)

Review https://www.fixtrading.org/standards/fast/ for more details.
Chris M

Order Execution » Order state change response Sep 10, 2019 @ 11:14 AM (Total replies: 3)

Do not use GTC flag for markets orders. We may allow this in simulated environment but some real futures exchange will reject your order. Market orders will either fill right away or reject if not appropriate. I'm showing the orders were sent with states of Sent, Accepted, Working, and Completed. All 9 orders sent today followed this staging of events. Are you getting this event with OEC Advanced Example app, but not your app named "TradeStreategy" [SIC]?
Chris M

API Support » Can't connect to the FAST price server Aug 29, 2019 @ 04:19 PM (Total replies: 3)

GAIN Futures FIX/FAST Price Server is built according FAST Specification Version 1.1 and FAST Session Control Protocol 1.1. Did you follow logon message as described here https://gainfutures.com/GFAPI/html/85a85b48-62ff-44c8-9b81-46c943b1fa5d.htm?

I don't see logon message. Are you sending to the following server?

Stage environment: api.gainfutures.com, port 9301

FAST-IN: Logon -> {63, A, 20190829210953, 30, BridgeTest, , }
Chris M

API Support » Excel DDE Add-in not found Aug 27, 2019 @ 04:31 PM (Total replies: 1)

DDE plugin is not a Developer tool, it is a client plugin available in the demo and live platforms. Download here: https://gainfutures.com/gain-trader/download.

As a reminder, we're no longer releasing updates on OEC Trader Developer. We will be releasing GAIN Trader Developer 4.0 soon and encourage all developers to use GFAPI as OECAPI applications will be required to migrate to the new API mid-2020.
Chris M

API Support » OEC Trader Developer 3.5 and API for Developer doesn't seem to work well Jul 08, 2019 @ 10:57 AM (Total replies: 4)

Trailing stop orders are still impacted and will be resolved in our next release.
Chris M

API Support » GAIN API COM support Jun 28, 2019 @ 08:23 AM (Total replies: 2)

API COM will be coming soon. Only new .NET version has been released.
Chris M

Announcements » The beta version of GF API has been released Jun 27, 2019 @ 03:37 PM (Total replies: 0)

We're happy to announce the beta version of GF API has been released. We
encourage you to start efforts writing to our new API.

* Download the package at: https://www.nuget.org/packages/GFAPI/
* Samples can be found on our Bitbucket page at: https://bitbucket.org/GainFuturesDev/
* Documentation can be found at: https://gainfutures.com/GFAPI

If you have questions, please post on our API Forum at: https://apisupport.gainfutures.com/

Once your development is complete, please reply to this email so we can
provide Conformance details.

As a reminder, we will support the current OEC API up until June 2020.
No additional development or updates will be released to OEC API and we
will decommission OEC API after 12 months from this annoucement. All
new development and major updates will be released to our new GF API.
For vendors who have written to us via FIX, the new GF API will not
impact your application.
Chris M

API Support » Demo on how to use the API from gain capital. Jun 17, 2019 @ 09:32 AM (Total replies: 1)

We offer connectivity via FIX and .NET API. Both offer access to our price feed. We provide samples of both on our Bitbucket pages: https://bitbucket.org/GainFuturesDev/

You may review documentation at: https://gainfutures.com/api/index.html

.NET API post on market data: https://gainfutures.com/api/html/4e2865e8-7ac9-457e-8d5a-6d930f3408a8.htm
Chris M

API Support » "Top Of Market" is unreachable May 28, 2019 @ 03:19 PM (Total replies: 1)

All Developers accounts come with CME Market Depth data. We unable to entitle these accounts with Top of Book data. This data plan is only available in public simulation and production environments.
Chris M

API Support » Missing Reference in COM API Sample May 28, 2019 @ 02:56 PM (Total replies: 1)

I do not replicate such issue. Did you obtain the COM sample from https://bitbucket.org/GainFuturesDev/comapisamples/src?

Please be aware that OEC API will be decommissioned in the future. We will be introducing GF API, see annoucement https://apisupport.gainfutures.com/Topic/Index/1223. If you haven't started development, it might be best to wait for new GF API details. This may be available as early as June 2019. Otherwise, if you write to OEC API, you'll need to write to GF API as well.
Chris M

API Support » m_Client_OnSymbolLookupReceived's Contracts returns nothing for m_Client.SymbolLookup ESM9 Mar 26, 2019 @ 03:45 PM (Total replies: 7)

This was sent to live customers (including your personal email address) on 18-Oct-2018.
Chris M

API Support » m_Client_OnSymbolLookupReceived's Contracts returns nothing for m_Client.SymbolLookup ESM9 Mar 26, 2019 @ 03:43 PM (Total replies: 7)


We sent customers notice about two-digit year. If you updated the DLL of the API, it now requires two-digit year, whereas older API version you used to build application can still use single-digit year for symbol.

Nuget has older API which supports single-digit year - https://www.nuget.org/packages/OECAPI/

Symbol format to require two-digit year

Dear Valued Customers

Effective October 20, 2018, the GAIN Futures trading platform will prompt
for a software update. We recommend that you perform this update.

The symbol format will change to the following:
Base Symbol + Month Code + Two-digit year

For example, the e-mini S&P format would change from ESU8 to ESU18.

If you are using third-party software, this change may not take place
until the software vendor updates to our latest API version.

If you have any questions, please contact your Introducing Broker.


GAIN Futures Client Services
Chris M

API Support » m_Client_OnSymbolLookupReceived's Contracts returns nothing for m_Client.SymbolLookup ESM9 Mar 19, 2019 @ 03:44 PM (Total replies: 7)

This issue has been resolved and released. Please check again.
Chris M

API Support » OnSymbolLookupReceived returns empty instruments list Mar 19, 2019 @ 03:43 PM (Total replies: 4)

This issue has been resolved and released.
Chris M

API Support » Unable to resolve symbol Feb 28, 2019 @ 12:52 PM (Total replies: 2)

If you're using latest version of API, you need to use two-digit year in symbol. Eg. ESH19 instead of ESH9.
Chris M

Announcements » New GF API coming in Q2 2019 Jan 04, 2019 @ 11:57 AM (Total replies: 4)

You will be able to use OEC COM API while GF COM API is being developed. There will not be a gap in COM API coverage.
Chris M