Betfair Exchange Games API services and descriptions
REST services are stateless by nature requiring the username and password to appear as a parameter and a field in the header of some requests to access the Exchange Games API Services (URIs). For access to these restricted resources you also have to include your application's identifier details in the header as specified in the API documentation.
Name
Description
api
The 'api' service is the root element (or 'home page') of the Exchange Games API. It provides links to the high-level services for accessing information on games, accounts and bets, as well as the API schema and the 'ping' test service.
schema
The 'schema' service returns the Exchange Games API XML Schema Definition document (XSD) which defines the data structures that the API expects and returns in response to requests.
ping
The 'ping' service returns the API operating status and the results of a user credential test if they are provided in the request.
channelLanding
The 'channelLanding' service returns a list of resources for retrieving further information about the games - each channel delivers a particular game type.
channelInfo
The 'channelInfo' service provides round times for each active channel as well as a description on how the game data is represented.
channelSnapshot
The 'channelSnapshot' service provides current information for a game in progress and the betting market(s) in operation for it.
channelHistory
The 'channelHistory' service provides information for completed games.
accountLanding
The 'accountLanding' service returns a list of resources for retrieving further information about a user's Exchange Games account and making transfers into or out of it.
accountSnapshot
The 'accountSnapshot' service provides current balance information for a user's account.
accountStatement
The 'accountStatement' service provides transactional information for a user's account.
postTransferOrder
The 'postTransferOrder' service requires an HTTP post request submitting XML data (in a format specified by the schema element of the same name) for moving money into or out of a user's Exchange Games account.
betLanding
The 'betLanding' service returns a list of resources for retrieving further information about users' bets as well as placing, editing and cancelling them.
betSnapshot
The 'betSnapshot' service provides information on a user's current outstanding bets.
betHistory
The 'betHistory' service provides infromation on a user's past bets.
postBetOrder
The 'postBetOrder' service requires an HTTP post request submitting XML data (in a format specified by the schema element of the same name) for placing, editing and cancelling bets.
