Mock sample for your project: Soccer v3 Projections API

Integrate with "Soccer v3 Projections API" from sportsdata.io in no time with Mockoon's ready to use mock sample

Soccer v3 Projections

sportsdata.io

Version: 1.0


Use this API in your project

Integrate third-party APIs faster by using "Soccer v3 Projections API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
It also helps reduce your dependency on third-party APIs: no more accounts to create, API keys to provision, accesses to configure, unplanned downtime, etc.

Description

Other APIs by sportsdata.io

LoL v3 Projections

sportsdata.io
LoL v3 Projections

NBA v3 RotoBaller Articles

sportsdata.io

MLB v3 Stats

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

NFL v3 RotoBaller Articles

sportsdata.io

CS:GO v3 Scores

sportsdata.io
CS:GO v3 Scores

NHL v3 Stats

sportsdata.io

CFB v3 Scores

sportsdata.io
CFB schedules, scores, team stats, odds, weather, and news API.

NFL v3 Stats

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

NFL v3 Projections

sportsdata.io
NFL projected stats API.

NBA v3 Scores

sportsdata.io

Golf v2

sportsdata.io

MLB v3 Scores

sportsdata.io
MLB scores API.

Other APIs in the same category

MLB v3 Projections

sportsdata.io
MLB projections API.

Hydra Movies

hydramovies.com
Hydra Movies is a streaming service that holds information on thousands of popular movies.
The Hydra Movies API gives you access to their entire collection of full movies.
Each film returned provides you with the following data:
Movie Title
Movie Release Year
Genre
Movie Summary
Movie Poster
IMDB ID
IMDB Rating
Runtime
Language
YouTube trailer

NBA v3 Play-by-Play

sportsdata.io
NBA play-by-play API.

Bets API

The Bets API methods are used to place single, multiple and complex bets and to retrieve a customer’s bet history. When retrieving a customer’s bet history you can organize the bets from the betting history in terms of date, bet type and whether the bet is settled or not. You can also specify what fields to be included/excluded or return a list of all default fields the method returns. The Bets API will also generate a bet delay if you’re placing a single/multiple bet in-Play by creating a time margin to negate the effects of major changes to the market (for example, goals during a football match). Note that in version 2 of our APIs, Bets API contains the functionality of both Bets API v1 and the Betslips API v1.

NBA v3 Scores

sportsdata.io

Golf v2

sportsdata.io

NBA v3 RotoBaller Articles

sportsdata.io

Profile

haloapi.com
API that provides Profile information about Players.

CS:GO v3 Stats

sportsdata.io
CS:GO v3 Stats

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.

NFL v3 Scores

sportsdata.io
NFL schedules, scores, odds, weather, and news API.

NBA v3 Stats

sportsdata.io