Mock sample for your project: NFL v3 Scores API

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

NFL v3 Scores

sportsdata.io

Version: 1.0


Use this API in your project

Speed up your application development by using "NFL v3 Scores 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.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.

Description

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

Other APIs by sportsdata.io

MLB v3 Play-by-Play

sportsdata.io
MLB play-by-play API.

Soccer v3 Stats

sportsdata.io

Soccer v3 Projections

sportsdata.io

NBA v3 Projections

sportsdata.io

NBA v3 RotoBaller Articles

sportsdata.io

NFL v3 RotoBaller Articles

sportsdata.io

CS:GO v3 Stats

sportsdata.io
CS:GO v3 Stats

MLB v3 Stats

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

CBB v3 Scores

sportsdata.io

Golf v2

sportsdata.io

MLB v3 Projections

sportsdata.io
MLB projections API.

NHL v3 Stats

sportsdata.io

Other APIs in the same category

UGC

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

Numbers API

whapi.com
The William Hill Numbers API uses a single method that allows you to generate random numbers for your application. Numbers can either be unique or can be produced with the chance that some might be the same. For example, you can have a highest value of 6 and a lowest value of 1 with a count of 2 with a unique value of false - this will give you two numbers between 1 and 6 which are independent, just like two dice being rolled. The Numbers API is a Private API and therefore not automatically available to developers. To use this API, contact your business manager who will guide you through the separate Terms and Conditions of use before you can have the API assigned to your application.

NFL v3 RotoBaller Premium News

sportsdata.io

Golf v2

sportsdata.io

Metadata

haloapi.com
API that provides Metadata information.

Profile

haloapi.com
API that provides Profile information about Players.

Jokes One API

Jokes One API offers a complete feature rich REST API access to its jokes platform. This is the documentation for the world famous jokes API. If you are a subscriber and you are trying this from a console add 'X-JokesOne-Api-Secret' header and add your api key as the header value. You can test and play with the API right here on this web page. For using the private end points and subscribing to the API please visit https://jokes.one/api/joke/.

NBA v3 Play-by-Play

sportsdata.io
NBA play-by-play API.

CBB v3 Stats

sportsdata.io

NPR Sponsorship Service

Sponsorship for non-NPR One client applications

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.