Mock sample for your project: Hydra Movies API

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

MLB play-by-play API.

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.

CS:GO v3 Scores

Introduction
Whether you're looking to build an official Pandascore integration for your service, or you just want to build something awesome, we can help you get started.
The API works over the HTTPS protocol, and is accessed from the api.pandascore.co domain.
The current endpoint is https://api.pandascore.co.
All data is sent and received as JSON by default.
Blank fields are included with null values instead of being omitted.
All timestamps are returned in ISO-8601 format
About this documentation
Clicking on a query parameter like filter or search will show you the available options: filter
You can also click on a response to see the detailed response schema: response
Events hierarchy
The PandaScore API allows you to access data about eSports events by using a certain structure detailed below.
Leagues
Leagues are the top level events. They don't have a date and represent a regular competition. A League is composed of one or several series.
Some League of Legends leagues are: EU LCS, NA LCS, LCK, etc.
Some Dota 2 leagues are: ESL One, GESC, The International, PGL, etc.
Series
A Serie represents an occurrence of a league event.
The EU LCS league has two series per year: spring 2017, summer 2017, spring 2016, summer 2016 etc.
Some Dota2 Series examples would be: Changsha Major, Open Bucharest, Frankfurt, i-League Invitational etc.
Tournaments
Tournaments groups all the matches of a serie under "stages" and "groups".
The tournaments of the EU LCS of summer 2017 are: Group A, Group B, Playoffs, etc.
Some Dota 2 tournaments are: Group A, Group B, Playoffs, etc.
Matches
Finally we have matches which have two players or teams (depending on the played videogame) and several games (the rounds of the match).
Matches of the group A in the EU LCS of summer 2017 are: G2 vs FNC, MSF vs NIP, etc.
Matches of the group A in the ESL One, Genting tournamnet are: Lower Round 1, Quarterfinal, Upper Final, etc.
Please note that some matches may be listed as "TBD vs TBD" if the matchup is not announced yet, for example the date of the Final match is known but the quarterfinal is still being played.
Structure
Formats
The API currently supports the JSON format by default.
Other formats may be added depending on user needs.
Pagination
The Pandascore API paginates all resources on the index method.
Requests that return multiple items will be paginated to 50 items by default. You can specify further pages with the page[number] parameter. You can also set a custom page size (up to 100) with the page[size] parameter.
The Link HTTP response header contains pagination data with first, previous, next and last raw page links when available, under the format
Sorting
All index endpoints support multiple sort fields with comma-separation (,); the fields are applied in the order specified.
The sort order for each field is ascending unless it is prefixed with a minus (U+002D HYPHEN-MINUS, “-“), in which case it is descending.
For example, GET /lol/champions?sort=attackdamage,-name&token=YOURACCESSTOKEN will return all the champions sorted by attack damage.
Any champions with the same attack damage will then be sorted by their names in descending alphabetical order.
Rate limiting
Depending on your current plan, you will have a different rate limit. Your plan and your current request count are available on your dashboard.
With the free plan, you have a limit of 1000 requests per hour, others plans have a limit of 4000 requests per hour. The number of remaining requests is available in the X-Rate-Limit-Remaining response header.
Your API key is included in all the examples on this page, so you can test any example right away. Only you can see this value.
Authentication
The authentication on the Pandascore API works with access tokens.
All developers need to create an account before getting started, in order to get an access token. The access token should not be shared.
Your token can be found and regenerated from your dashboard.
The access token can be passed in the URL with the token query string parameter, or in the Authorization: Bearer header field.

API that provides statistical data about Players and Matches.

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 projected stats API.