Mock sample for your project: MLB v3 RotoBaller Premium News API

NBA play-by-play API.

NFL play-by-play API.

NFL projected stats API.

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

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

CS:GO v3 Scores

The interface to our OAuth2 server

API that provides Metadata information.

REST API about Fortnite game

EVEMarketer Marketstat API is almost compatible with EVE-Central's Marketstat API.

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

CFB schedules, scores, team stats, odds, weather, and news 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.

Audio recommendations tailored to a user's preferences