Mock sample for your project: Betfair: Exchange Streaming API

Integrate with "Betfair: Exchange Streaming API" from betfair.com in no time with Mockoon's ready to use mock sample

Betfair: Exchange Streaming API

betfair.com

Version: 1.0.1423


Use this API in your project

Integrate third-party APIs faster by using "Betfair: Exchange Streaming API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
Improve your integration tests by mocking third-party APIs and cover more edge cases: slow response time, random failures, etc.

Description

API to receive streamed updates. This is an ssl socket connection of CRLF delimited json messages (see RequestMessage & ResponseMessage)

Other APIs in the same category

Sessions API

The William Hill Sessions API uses a central authentication service (CAS*) on all resources that require access to a customer’s account or betting functionality. To authenticate, you’ll need to supply a sportsbook username and password, in return you will be given an authentication ticket, which you can use on the majority of requests found within our services. The Sessions API should be used whenever you want to login a customer and: continue to use the William Hill API for that customer’s transactions use other CAS-enabled William Hill services outside the suite of APIs CAS is an enterprise Single Sign-On solution for web services (see https://wiki.jasig.org/display/CAS/Home). It is used by many William Hill services. Note: all requests must be executed over HTTPS and include an API key and secret. Authentication Ticket Expiration Times When a customer is logged in using the Sessions API, they are given an Authentication Ticket; using this ticket on subsequent API requests gives you access to account activities (such as placing a bet, deposits, etc). However, this ticket is only valid for a given period of time depending on how it is used. If the ticket is used and then has a period of inactivity longer than 7,200 seconds (2 hours), then the ticket will expire and further requests using the ticket will be denied - in effect, a customer has been logged out and will need to authenticate again. Normally, any ticket issued only has a maximum life expectancy of 28,000 seconds (8 hours) after which it can no longer be used, even if it has been used regularly. The customer again will be effectively logged out and will need to authenticate again. If you wish to avoid this, you need to set the query parameter extended to Y, which will enable your application to generate a ticket valid for 60 days without expiring due to inactivity.

LoL v3 Stats

sportsdata.io
LoL v3 Stats

Locations

whapi.com
The Locations API is a collection of methods that support geographical information. The first method is an address lookup service for UK addresses. This service can be used to provide a new customer with a list of possible addresses from which they can populate a registration form.

UGC

haloapi.com
API that provides Metadata about User-Generated Content (Maps and Game Variants).

SportsData API

The William Hill SportsData REST API is a collection of GET methods to provide William Hill product data such as sport, competition, event, market and selection data (including prices).

Soccer v3 Projections

sportsdata.io

NHL v3 Play-by-Play

sportsdata.io
NHL play-by-play API.

NBA v3 RotoBaller Premium News

sportsdata.io

CS:GO v3 Scores

sportsdata.io
CS:GO v3 Scores

Betfair: Exchange Streaming API

API to receive streamed updates. This is an ssl socket connection of CRLF delimited json messages (see RequestMessage & ResponseMessage)

NHL v3 Scores

sportsdata.io

CBB v3 Stats

sportsdata.io