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

NFL v3 Projections

sportsdata.io
NFL projected stats API.

MLB v3 RotoBaller Premium News

sportsdata.io

NBA v3 Projections

sportsdata.io

NPR Sponsorship Service

Sponsorship for non-NPR One client applications

MLB v3 Stats

sportsdata.io
MLB scores, stats, and news API.

NASCAR v2

sportsdata.io

NFL v3 Stats

sportsdata.io
NFL rosters, player stats, team stats, and fantasy stats API.

RAWG Video Games Database API

rawg.io
The largest open video games database.
Why build on RAWG
More than 350,000 games for 50 platforms including mobiles.
Rich metadata: tags, genres, developers, publishers, individual creators, official websites, release dates,
Metacritic ratings.
Where to buy: links to digital distribution services
Similar games based on visual similarity.
Player activity data: Steam average playtime and RAWG player counts and ratings.
Actively developing and constantly getting better by user contribution and our algorithms.
Terms of Use
Free for personal use as long as you attribute RAWG as the source of the data and/or images and add an active
hyperlink from every page where the data of RAWG is used.
Free for commercial use for startups and hobby projects with not more than 100,000 monthly active users or 500,000
page views per month. If your project is larger than that, email us at [email protected] for
commercial terms.
No cloning. It would not be cool if you used our API to launch a clone of RAWG. We know it is not always easy
to say what is a duplicate and what isn't. Drop us a line at [email protected] if you are in doubt,
and we will talk it through.
You must include an API key with every request. The key can be obtained at https://rawg.io/apidocs.
If you don’t provide it, we may ban your requests.
Read more.

NPR Station Finder Service

Allows clients to look up NPR member station information

Hubhopper Partner Integration API(s) - Production

hubhopper.com
This is an interactive document explaining the API(s) that could be used to fetch data from Hubhopper. Use the api key provided to authorize x-api-key and test the API(s). The output data models are also available for reference.

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.

Soccer v3 Stats

sportsdata.io