Mock sample for your project: NASCAR v2 API

Integrate with "NASCAR v2 API" from sportsdata.io in no time with Mockoon's ready to use mock sample

NASCAR v2

sportsdata.io

Version: 1.0


Use this API in your project

Start working with "NASCAR v2 API" right away by using this ready-to-use mock sample. API mocking can greatly speed up your application development by removing all the tedious tasks or issues: API key provisioning, account creation, unplanned downtime, etc.
It also helps reduce your dependency on third-party APIs and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.

Description

Other APIs by sportsdata.io

NHL v3 Scores

sportsdata.io

NBA v3 Play-by-Play

sportsdata.io
NBA play-by-play API.

NHL v3 Projections

sportsdata.io

CS:GO v3 Stats

sportsdata.io
CS:GO v3 Stats

NFL v3 Stats

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

Soccer v3 Projections

sportsdata.io

CFB v3 Scores

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

MLB v3 Scores

sportsdata.io
MLB scores API.

LoL v3 Stats

sportsdata.io
LoL v3 Stats

NBA v3 RotoBaller Articles

sportsdata.io

NFL v3 RotoBaller Premium News

sportsdata.io

NBA v3 Scores

sportsdata.io

Other APIs in the same category

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.

Soccer v3 Stats

sportsdata.io

UGC

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

Listen API: Podcast Search & Directory API

Simple & no-nonsense podcast search & directory API. Search all podcasts and episodes by people, places, or topics.

NPR Sponsorship Service

Sponsorship for non-NPR One client applications

NFL v3 Stats

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

NHL v3 Projections

sportsdata.io

LoL v3 Stats

sportsdata.io
LoL v3 Stats

CBB v3 Stats

sportsdata.io

LoL v3 Projections

sportsdata.io
LoL v3 Projections

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.

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.