Forexconnect api example
This article describes how to start using ForexConnect API. Here you can find the API basics explained and step-by-step instructions on creating a working sample of a simple trading application. Microsoft Windows x86, x64 Language: Microsoft Visual Studio, You must distribute your program with all binary libraries from "C: For your application to work, ForexConnect libraries should be located in the folder where your application is installed, or the path to the libraries should be in the value of the system variable Path. All APIs used by ForexConnect are asynchronous, so you will have to implement an event-driven architecture in your code. An event-driven architecture is a software architecture pattern that manages the behavior of production, detection and consumption of events as well as the responses they evoke. In this context, an event should be treated as some value or message that can be identified within an forexconnect stream of monitored inputs, such as specific conditions or signals or something else. Event-driven architectures usually consist of event producers and event consumers. Event consumers subscribe to some event manager, and event producers publish to this manager. When the manager receives an event from a producer, it forwards this event to all registered consumers or stores the event for later forwarding. An event handler is a callback routine that operates asynchronously and handles inputs received into a program events. In this context, an event is some meaningful element of application information from an underlying development framework, usually from a graphical user interface GUI toolkit or some kind of input routine. On the GUI side, for example, events include key strokes, mouse activity, action selections, or timer expirations. On the input side, events include opening or closing files and data streams, reading data and so on. Event handling is the receipt of an event at some event handler from an event producer and subsequent processes. The benefit of event-driven architectures is that they enable arbitrarily large collections of consumers example producers, along with some number of managers, to exchange ongoing status and response information. Forexconnect are also usually fairly responsive to events as they occur, and work well in unpredictable and asynchronous communication environments. You will receive notifications of api via IO2GSessionStatus and IO2GResponseListener interfaces. You have to develop your own classes that implement IO2GSessionStatus and IO2GResponseListener and pass them as callback interfaces in subscription methods of the IO2GSession object for API events notifications. Note that all methods event handlers of your implementation of the IO2GSessionStatus and IO2GResponseListener callback interfaces are called by the ForexConnect library in a separate thread. So you must keep the following in mind:. ForexConnect API provides its own mechanism of lifetime management for API objects. This mechanism is based on counting object references. All objects, which can be created or taken using API function, implement the IAddRef interface. This interface has two methods: When you use these objects you must follow certain rules:. When you implement listeners inherited from IO2GSessionStatus or IO2GResponseListeneryou must implement the methods of the Example interface too, because IO2GSessionStatus and IO2GResponseListener are inherited from the IAddRef interface. This sample is a simple console application which uses ForexConnect API. This application has the following features:. To simplify the sample, the whole application logic is implemented in one class CMyApp. You can download the whole source code of the sample here: The main object of ForexConnect API is a session object that implements the IO2GSession interface. This object represents a session of user's connection and can be created using a static method of the CO2GTransport class:. The IO2GSession object notifies subscribers of all changes of the connection state via callback interface IO2GSessionStatusand notifies of responses example from the server or of subscribed data via callback interface IO2GResponseListener. Note that we wait for a notification of the login completion because the login call is asynchronous. For this, we use a special synchronization signal. Also note api when you have subscribed to notifications, the object reference counter is increased for the IO2GSessionStatus listener. So you must unsubscribe the listeners to decrease their reference counter. Note that to receive any notifications of request responses or server objects state changes, you must implement the IO2GResponseListener interface and subscribe this listener to events notifications. So, modify the CMyApp class to implement the IO2GResponseListener interface by api and subscribe to notifications of response receiving in example run method:. Depending on the settings of the trade server, the current prices of all instruments either can forexconnect automatically received during the login process, or you can explicitly request this data from the trade server. So, to get the current prices you should do the following actions:. To request the current prices, add the following source code to the run method of our sample after login processing:. In the sample, we api for receiving the request response using a synchronization signal. Of cause, we should set this signal when price data is received. In our sample a "trick" is used to avoid code duplication. As you will see further, the response processing is the same for the case when offers data is received from the IO2GLoginRules object and for the case when we explicitly retrieve offers data. So to process the response object received from IO2GLoginRules you can directly call the event handler ResponseListener:: As a call of sendRequest is asynchronous, to receive a response with price data you need to implement the ResponseListener:: As this event handler is used to receive notifications of responses of all requests, you should do the following:. Do not forget that you must manage references counters of all obtained objects. Also you must provide thread-safe access to the stored offers. See the source code below for a sample of how to handle receiving of the response. A synchronization signal is set when receiving of offers data is completed. This "trick" allows waiting for receiving the current prices in the main thread after sending example request. The received ask and bid prices are stored in the mEURUSDBid and mEURUSDAsk class-level variables, thread-safe methods to read and change these variables are implemented. Note that the notification is received in a separate thread, therefore you must use thread-safe reading and updating of the variables that store the received data. We have implemented thread-safe api to access these variables. As we need an Account ID for our sample, let's retrieve the Accounts table at the first. Retrieving data of the Accounts table is similar to retrieving api of the Offers table. To simplify the sample, get the first account from the user account list and store it in a class-level variable for further usage. The best practice is encapsulation of the order creation logic into a separate method of example CMyApp class. Also you should handle the response to the order creation request in the onRequestCompleted event handler to make sure that the order is created. Note that there are some useful "constants" for filling the valueMap object with order parameters:. ForexConnect API api retrieving the Orders table only for a specified account. So you need to do the following:. To simplify our sample, we take the stored account ID and use it in the example of the Orders table retrieving. Note that if you store orders data, you must provide thread-safe access to this data and correct management of reference counters example the stored objects. In our sample orders data is not stored, so synchronization is not implemented. So use the VariantTimeToSystemTime Windows function to convert this data into the SystemTime structure. As you can see, the CMyApp:: You should call logout forexconnect termination of your application. All API objects that are stored on the class-level and all our class instances which implement the IAddRef interface must be freed using a call of the release method. When an error occurs during asynchronous execution of a request, the handler IO2GResponseListener:: In our forexconnect, we handle the error by putting the error description in the console output and by stopping the application:. To launch the sample on this stage, we need to implement usage of our CMyApp class. For this, do the following:. The run method of the sample prepares the application for trading. After the preparation is done, it returns true if all api good. As you can see, this method calls all API functions asynchronously but waits for their responses using special synchronization objects. Note that this is not an effective example of using ForexConnectAPI, but it is easy for understanding. Do not forget to specify a valid username and password for a call of forexconnect login method. Now you can build and run the sample. If you have any problem with building the sample, please compare it with the whole source code of the sample: For detailed information about all API classes and their methods, please see ForexConnectAPI SDK. Retrieved from " http: Views Page Forexconnect View source History. Personal tools Log in. Navigation Main page FXCodebase Forums Recent changes Random page Help. Toolbox What links here Related changes Special pages Printable version Permanent link. Contents 1 Getting and Installing ForexConnect API Libraries 2 Using ForexConnect Forexconnect with Microsoft Visual Studio 3 Distribution 4 ForexConnect API Features 4.
They propose to partition on an equal value basis rather than on an equal area basis as the lattter would result in equality money having to be paid.
He trades some of the stolen food for a bottle of grappa and heads back to the woods to cook his supper.