HOW DO I GET ACCESS TO THE API?
- Have a fully verified BETDAQ account
- Have a minimum of £/€/$200 in your account
- Complete the onboarding form below or click here
BETDAQ does not charge for the API, but users are expected to contribute to the exchange relative to their usage of the API. Customers found to be making a high volume of calls without the levels of business to justify them will have their permissions removed.
Our WSDL can be found - http://api.betdaq.com/v2.0/API.wsdl
View Sample Application Below:
The sample application is intended to show how the API is used by showing how to call some Read Only and Secure methods.
It is a window application made in C# (.NET 1.1).
In this sample application we use the following BETDAQ ReadOnly API Methods: Get Top Level Events, Get Event Sub Tree No Selections, Get Market Information, Get Prices.
And the following BETDAQ Secure API Methods: GetAccount Balances, PlaceOrdersNoReceipt, CancelAllOrders, CancelOrders, ListBootstrapOrders, ListOrdersChangedSince.
The sample application provides code demonstrating how to call most of the key web methods and use the data structures returned. The application is broken into two projects; the first (GBE_UserInterface) is concerned only with the user interface of the windows form application. The second project (GBE_Data) provides agents (e.g. ReadonlyServiceAgent) for wrapping all calls to the API and converters (e.g. EventConverter) to translate the API’s types (EventClassifierType) into local types (Event).
As you will quickly realise, this sample application demonstrates only a subset of method calls, requires fine-tuning, and is far too simple to be used in a real world situation, its goal is simply to demonstrate the intended approach to using version 2.0 of the Global Betting Exchange API.
Each API call follows the standard request/response pattern, as can be seen by looking at the WSDL for the API (Figure 1). For example, to use the web method ListSelectionsChangedSince you first construct a ListSelectionsChangedSinceRequest object, and set the SelectionSequenceNumber. The web method then returns a ListSelectionsChangedSinceResponse object, which in this case contains a collection called Selections of type ListSelectionsChangedSinceResponseItem.
It should also be noted that every response object derives from BaseResponse which contains a ReturnStatus object that contains meta data about the web method call, for example whether an error was encountered.