## Copa America Live Scores The Copa America APIs allows to retrieve matches results, scorers, lineups, substitutes, events, statistics, adds and much more all with live updates. For any doubt or problem using the API, open an API Support ticket to get an answer in a blink. See below the list of its unique features. Have fun! The Copa America Ninja Team ## Season results It's possible to retrieve all the matches data calling the endpoint /api/copaamaerica You can call the API -without submitting any parameter, to get all the matches for the day (if there isn't any match for the day you will get a 500 server error, that is the call don't increment your quota for the day) -submitting the parameter `date`, to retrieve the matches for that date (in the format mmddyyyy) -submitting the parameter `team1`, to retrieve the matches that the team has played at home (together with `team2` return that very match) -submitting the parameter `team2`, to retrieve the matches that the team has played away (together with `team1` return that very match) -submitting the parameter `matchday`, to retrieve the matches for that round 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 `"time":"AET"` *after extra time* or `"time":"PENALTIES"` *after penalties*) or not already played matches, and the ended ones only after a while the matches are really finished (usually always within 24 hours); if you need live updates you have to set the`live` parameter to *true* (in this case `time` returns the minute for the match), if there isn't any playing match for the parameters specified, the API give you the 500 error message 'No games found'. *Take in mind that a live request can continue to give you the result even after a while, usually some hours, a match is finished; as soon as the API stop to give you the result for the match, you can get the result again removing the live parameter.* ## Lineups, substitutes and coaches It's possible to get data about teams players and coaches for a game using the following API /api/worldcup/formations The API requires two mandatory attributes, team1 and team2 to select the game of interest. The result is a JSON object with two properties, team1 and team2, where each *team* property is an object containing the teamName and the players 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 lineups and substitutes with each array item equals to an object containing the playerNamber, that is the shirt number for the player and the playerName attribute. *Captain players are identified by the property isCaptain.* **You can get the formations starting from 30 minutes before a match start using the`live` parameter set to *true***, if the API give you the 500 error message, that means the game is already finished from a while or it's not playing or not going to play. *Take in mind that a live request can continue to give you the result even after a while, usually some hours, a match is finished; as soon as the API stop to give you the result for the match, you can get the result again removing the live parameter.* The APIs can either respond with a 500 error if doesn't exist a match ifor them team1 and team2 parameters in the request (values are case sensitive, use the matches results requests to find out valid values to use). ## Match scorers It's possible to get all the scorers for a match with a single API call. The API requires two mandatory parameters team1 *that is the home team name* and team2 *that is the away team name* plus an optional one live to get live updates with frequency according your plan. (to set with the values returned by the season results API). 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: isPenalty *true if the goal is scored from a penalty, default false (that is if the attribute doesn't exist)* isOwn *true if the goal is an own goal, default false* isFromCorner *true if the goal is scored from a corner, default false* isFreekick *true if the goal is scored from a free kick, default false* isLeftFoot *true if the goal is scored by left, default false* isRightFoot * true if the goal is scored by right, default false* isHead *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 goals attribute will be an empty array. ## Match events The 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` `2ND-Yellow-Card` `Red-Card` `In` and `Out` (substitutions) `Missed-Penalty` (player fail to score a penalty) `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` `Penalty-Won` (the player that won the penalty) `Penalty-Commited` (the player that committed a penalty foul) `Changed-Captain` (the new captain player if the previous goes out) All *teams* and *players* events give you the *minute* the event occurred, *teams* events have a *value* attribute more that get the value for the event (the team module), *players* events instead a list of players name related to the event. As usual the API let you to get live updates using the proper parameter, I you don't specified the live parameter you get the data only after a while the match is finished (usually within few hours), otherwise you get live updates according your subscribed plan. As soons as the live API stops to give you an answer you can continue to get data for the match removing the live parameter. ## Match statistics The API requires two mandatory parameters team1 *the home team name for the match* team2 *the away team name for the match* In the JSON response you can find the following impressive amount of statistics for each team of the match selected:

totalSaves touches aerialsWon passesTotal passesSuccessful cornersTotal cornersAccurate tackleSuccessful throwInsTotal

aerialsTotal offensiveAerials defensiveAerials shotsOffTarget tacklesTotal dribblesLost shotsTotal shotsBlocked

dribblesAttempted dribbledPast dispossessed foulsCommited shotsOnTarget offsidesCaught tackleUnsuccesful interceptions dribblesWon clearances possession

goals foulsWon penatyWon penaltyCommited

As usual you can get live updates using the proper parameter. ## Missing players for a match The API Missing players for a match requires two parameters team1 and team2, and returns a response a few days before a match with updates till the match starts. 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 the match with the reason. If there is any doubt about the player will play the match the reason will be inside square brackets, otherwise the reason will be with no bracket. Typical reasons are * **Injured**, **Suspended**, **Unfit**, **Other***. ## Push notifications You can subscribe to a match starting from 24 hours to 5 minutes before the start. As soon as you subscribe will be sent to your url in HTTP POST a token string you have to return back via the activate endpoint within 10 minutes from the subscribe time. Using the list endpoint you can see all the matches you have correctly subscribed. Take in mind that if the push notifications fails more than 3 times to contact your url (timeout about 10 seconds), that subscribed event will be automatically removed. Each call to the subscribe endpoint will add 20 to your dailing quota.