Euro Cup 2016 Live Scores

PAID
By Simone | Updated a year ago | Entertainment

Euro Cup 2016 Live Scores Overview

Followers: 38
Resources:
Terms of use
API Creator:
avatar
Simone
heisenbug
Rate API:
Log In to Rate API

README

Euro Cup Scores API allows retrieving all results, scorers, lineups, substitutes, events, statistics, and much more all with live updates, for the next upcoming European Cup.

It’s possible to retrieve all the matches results calling the endpoint
<a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#matches-results”>/api/eurocup</a>
this kind of request requires the mandatory parameter match day to retrieve all the matches at the given round.
Match day from 1 to 3 are matches of the group stages, 4 is 1/8 finals, 5 is quarter finals, 6 is semi finals and 7 is for the final.
If matches are already played, the API will give you data about red cards number if any, referee, final and first half scores too, otherwise only the matches that will be played.

Take in mind that this API returns only final results ("time":"FT") or not already played matches, and the final ones only after a while the matches are really finished (usually after few minutes); if you need live updates you have to query the Live version of the API that responds at the endpoint <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#matches-results-live”>/api/live/eurocup</a>.
The live version doesn’t require any parameter and returns all the matches still playing that is with real time updates; if there isn’t any playing match the API will give you the 500 error message ‘No Live matches at this time’.
The live version starts to give you an answer few minutes before the start and stop few minutes after the last playing match is over.

The <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#top-scorers”>/api/eurocup/table/scorers</a> let you the get the top five scorers for the cup.
The JSON result give you the player name, the number of goals scored in order from the first till the fifth and the number of ones scored by penalty.
You can either use the optional parameters like
<code>player</code> to get the result only for the <i>player</i> name specified (useful to get the number of goals scored by those players that aren’t in top 5)
<code>team</code> *to get top five scorers only for the specified <i>team</i> *

If you specify an invalid player name or a player name that hasn’t scored any goal yet, you will get an empty response, that is:

{"scorers":[]}

Using the endpoint API <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#group-table”>/api/eurocup/table</a> you will get the table for each group cup.
The table is compute considering all the finished games returned by the <a href="#wiki-matches-results">matches results</a> API (the one with no live updates) with match day between 1 and 3 (group stages).
The API requires the <code>group</code> mandatory parameter to specify the group you want the table for.
The API has the <code>time</code> optional parameter either you can submit to get the table considering only first half (FH) or second half (SH) result. Default is fun time (FT).

The JSON response give you data about the <code>team</code> name, the game <code>played</code>, <code>win</code>, <code>loss</code>, <code>goalsFor</code>, <code>goalsAgainst</code> and <code>points</code>.
The API at the moment don’t take into account any penalization a team could have to compute the total points number.

The <b>Euro Cup 2016 Live Scores</b> allows to retrieve matches results, scorers, lineups, substitutes, events, statistics and much more all with live updates.
<i>For any doubt or problem using the API, open an <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores/support/new”>API Support</a> ticket to get an answer in a blink.</i>
See below the list of its unique features.
Have fun!

<b>The Euro Cup Ninja Team</b>

The API <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#missing-players-for-a-match”>Missing players for a match</a> requires two mandatory parameters
<code>team1</code> and <code>team2</code>,
(you can either submit the optional parameter <code>match day</code> useful if a same match is played more times in the Cup, by default the API returns always the last match played)
and returns a response a few days before the match with continue updates till the match start.
Even after a match is played, the API continue to give you the last answer.
The response returns for each team the player name who will miss with the reason.
If there is any doubt about the player will play the match, the reason will be inside a square bracket, otherwise the reason will be with no bracket.
Typical reasons are Injured, Suspended, Unfit, Other.

The API requires two mandatory parameters
<code>team1</code> the first team name for the match
<code>team2</code> the second team name for the match
you can either submit the optional parameter <code>matchday</code> useful if a same match is played more times in the Cup, by default the API returns always the last match played.
In the JSON response you can find the following impressive amount of statistics for each team of the match selected:
<code>totalSaves touches aerialsWon passesTotal passesSuccessful cornersTotal cornersAccurate tackleSuccessful throwInsTotal</br>
aerialsTotal offensiveAerials defensiveAerials shotsOffTarget tacklesTotal dribblesLost shotsTotal shotsBlocked</br>
dribblesAttempted dribbledPast dispossessed foulsCommited shotsOnTarget offsidesCaught tackleUnsuccesful interceptions dribblesWon clearances possession goals foulsWon</code>
If a property is missing in the response its value is zero.

Take in mind that this API exists in two version, the one without live update <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#match-statistics”>/api/eurocup/match/stats</a> and the one with live update <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#match-statistics-live”>/api/live/eurocup/match/stats</a> with the second one one giving you real time statistics updates during the game and the first one giving you only the final statistics after a while the match is finished.

It’s possible to get all the scorers for a match with a single API call.
There are two version for this API, one without live update <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#match-scorers”>/api/eurocup/scores</a> that get you the answer after a while the game is finished (usually after few minutes), and the other <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#match-scorers-live”>/api/live/eurocup/scorers</a> with live updates, that give you the answer while the match is still playing (check the <a href="#wiki-matches-results">matches results</a> API live version to know the games with goals).
All of the two versions require two mandatory parameters
<code>team1</code> that is the first team name of the match
and
<code>team2</code> that is the second team name for the match
(<u>the names are the ones returned by the <b>matches results</b> API</u>)
you can either submit the optional parameter <code>matchday</code> useful if a same match is played more times in the Cup, by default the API returns always the last match played.

The JSON response contains the player name who scored the goal and the minute it was scored, more it can contains other attributes either that qualify better the kind of goal.
At the moment the attributes handled by the API are:
<code>isPenalty</code> true if the goal is scored from a penalty, default false
<code>isOwn</code> true if the goal is an own goal, default false
<code>isFromCorner</code> true if the goal is scored from a corner, default false
<code>isFreekick</code> true if the goal is scored from a free kick, default false
<code/>isLeftFoot</code> true if the goal is scored by left, default false
<code>isRightFoot</code> * true if the goal is scored by right, default false*
<code>isHead</code> true if the goal is scored by head, default false

The API give you an answer even if there isn’t any goal for a match, in that case the <code>goals</code> attribute will be an empty array.

It’s possible to get data about teams players and coaches for a game using one of the two following API versions
<a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#lineups-and-substitutes-for-a-match-live”>/api/live/eurocup/formations</a>
<a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#lineups-and-substitutes-for-a-match”>/api/eurocup/formations</a>
with the first one giving you the data as soon as the game starts (live version) till few minutes after the match end, and the second one after a while the game is finished.
The API requires two mandatory attributes, <code>team1</code> and <code>team2</code> to select the game of interest, you can either submit the optional parameter <code>matchday</code> useful if a same match is played more times in the Cup, by default the API returns always the last match played.
The result is a JSON object with two properties, <code>team1</code> and <code>team2</code>, where each team property is an object containing the <code>teamName</code> and the <code>players</code> properties, where the first one is the name of the team (equals to the one in the request) and the second one an object with the arrays <code>lineups</code> and <code>substitutes</code> with each array item equals to an object containing the <code>playerNamber</code>, that is the shirt number for the player and the <code>playerName</code> attribute.

The lineups players are ordered from goalkeeper to forward, to get more insight on how players are on the pitch see the events <code>Module-Start</code> and <code>Module-Change</code> you can get from the <a href="#wiki-match-events">match events</a> request without forgetting the attribute <code>position</code> returned by the <a href="#wiki-player-statistics-for-a-match">player match statistics API</a>.

The APIs will respond with a 500 error if doesn’t exist a match for them team1 and team2 parameters in the request (values are case sensitive, use the <a href="#wiki-matches-results">matches results</a> requests to find out valid values to use), or for the live version, if the game is not more playing.

It’s possible to get all the player statistics for a match using one of the two API version, the <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#player-stats-for-a-match”>no live</a> and the <a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#player-stats-for-a-match-live”>live</a> one, with the first giving you the result only after a while the game is finished (usually within few minutes) and the second you giving you the result starting from the first minute match, until the match is over, that is with live updates.
The APIs require three mandatory parameters
<code>team1</code> the first team name for the match
<code>team2</code> the second team name for the match
<code>player</code> the player name for which you want to know statistics
you can either submit the optional parameter <code>matchday</code> useful if a same match is played more times in the Cup, by default the API returns always the last match played.

The result is a JSON format response containing player infos like age, weight, height and player match stats like dribble won, fouls committed.
The complete data list handle at the moment from the API follows:
player info
<code>isManOfTheMatch, shirtNo, name, weight, age, height, isFirstEleven, position</code>
player match stats
<code>totalSaves, touches, aerialsWon, passesTotal, passesSuccessful, cornersTotal, cornersAccurate, tackleSuccessful, <br>
throwInsTotal, aerialsTotal, offensiveAerials, defensiveAerials, shotsOffTarget, tacklesTotal, <br>
dribblesLost, shotsTotal, shotsBlocked, dribblesAttempted, dribbledPast, dispossessed, <br>
foulsCommited, shotsOnTarget, offsidesCaught, tackleUnsuccesful, interceptions, dribblesWon, <br>
clearances,possession, goals, foulsWon</code>
If a property is missing in the response its value is zero.

For the <code>position</code> attribute you can get the following values:
GK = Goalkeeper
DM = Defensive Midfielder (1)
D = Defender (1)
M = Midfielder (1)
AM = Attacking Midfielder (1)
FW = Forward
Sub = substitute player

(1) the attribute value can have one letter more to specify better the field position, that is <code>C</code> for Center, <code>L</code> for Left and <code>R</code> for Right.

The Euro Cup 2016 Live Scores API let you trace two different kind of events
Team events
Module-Start (tell you the team module, that is how players are on the pitch, as soon as the match start)
Module-Change (tell you each module change occurred during the match)
Players events
Yellow-Card
Red-Card
In and Out (substitutions)
Missed-Penalty (penalty failed)
Saved-Penalty (keeper save a penalty)
Saved-Goal (player avoid an already done goal, clearance off the line)
Shot-On-Post
Error-Goal (player error that lead to a goal)
Assist-Goal (when a player intentionally do an assist that lead to a goal)
Goal-Disallowed

All teams and players events give you the minute the event occurred,
teams events have a value attribute that get the value for the event (the team module),
players events instead a list of players name related to the event.

There are two API version to get the data events, that is, with (<a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#match-events-live”>/api/live/eurocup/match/events</a>) or without live updates (<a href=“https://market.mashape.com/heisenbug/euro-cup-2016-live-scores#match-events”>/api/eurocup/match/events</a>).
The version without live update get you the data only after a while the match is finished (usually within few minutes), the one with live updates instead get you real time data and stop to get you an answer after few minutes the game is finished (at that time you get the answer querying the no live version).

All the two API versions require two parameters
team1 that is the first team name
and
team2 that is the second team name
and returns all the events for the two teams,
you can either submit the optional parameter <code>matchday</code> useful if a same match is played more times in the Cup, by default the API returns always the last match played.

Rating: 5 - Votes: 1