This is a collection of Rimble's raw data for League of Legends, CS:GO, DOTA 2, Valorant, Rocket League, Call of Duty, NBA2K, FIFA, and Siege, (the most popular eSports) as well as Cricket and Kabaddi. We provide upcoming matches as well as live and post-game information for world-wide professional leagues, along with other useful metadata and final game states - all with extremely low latency and high accuracy.
\nWe also do analytics and predictions for the above eSports (including player props and odds). To get access to the documentation for those endpoints, please contact us at support@rimble.io.
\nNOTE: This documentation page is only for raw data access to our REST API's (i.e. our upcoming and post-game information endpoints). For documentation on our live websocket for the above mentioned eSports, please contact us at support@rimble.io.
\nOur API only supports GET requests, and all requests must end with a trailing slash, “/”. To use this documentation page, from the top bar, select the programming language you are using to read in the data. This should give you example code for the endpoint on the right hand side panel, along with example responses. On the left hand side panel, we also give you descriptions for our data format.
Our endpoints require API key authentication where you have to provide a valid key to gain access. Reach out to us to get your access key.
\nYou may query for specific games using query parameters. For example, to query by gameid, you can add the following to the end of the URL (after the trailing slash, \"/\") ?matchid={matchid}. To query with multiple parameters, use the following syntax: ?date={YYYY-MM-DD}&team={team name}. The permitted query parameters for each endpoint are described in their respective sections below. We highly recommend making us of query parameters while accessing our endpoints (rather than using the base endpoint). This makes sure the size of the data being sent to you is manageable.
Note: While querying team and league names, spaces are permitted in the URLs.
\nIn this documentation, we use the word \"match\" to describe the event where two teams play each other. In many cases, this means that the two teams play a \"best of\"-style match i.e. each match usually comprises of more than one \"game\" as a part of it, and the team that wins the most games wins the match.
\nWe update all our data feeds hourly, and this is done 10 minutes past the hour. We recommend pulling the data at the same frequency. The best time to do this is at the stroke of the hour or 30 minutes past the hour.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Overview","slug":"overview"},{"content":"Authentication","slug":"authentication"},{"content":"Querying","slug":"querying"},{"content":"Relevant Terminology","slug":"relevant-terminology"},{"content":"Data Updates","slug":"data-updates"}],"owner":"16449503","collectionId":"fad6b30a-a390-42e8-8d05-b8b21bdfa273","publishedId":"Tzm8FvFw","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"449CAC"},"publishDate":"2021-07-12T20:34:23.000Z"},"item":[{"name":"League of Legends","item":[{"name":"Upcoming Matches","id":"4014d627-a807-4ff9-92ff-034a5b42dacc","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"Query Parameters: date, matchid, time, team, league.
Table 1: Match Data
\nTable 1.1: Match Format Data
\nTable 1.2: League Details Data
\nTable 1.3: Team Data
\nTable 1.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","lol","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"ff79ba07-1c7f-4554-8753-11635e2f7a4f","name":"lol-upcoming-matches-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for League of Legends. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","lol","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"67311b51-b318-4599-a6dc-50f0758cc4fe"},{"name":"Completed Matches","id":"fbf32291-8250-4768-b25c-339c1bf0ab31","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 2: Game Data
\nTable 2.1: Match Format Data
\nTable 2.2: League Details Data
\nTable 2.3: Team Data
\nTable 2.3.1: Team Results Data
\nTable 2.3.2: Player Data
\nTable 2.3.2.1: Player Results Data
\n","urlObject":{"protocol":"https","path":["raw","lol","completed-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"94e30b01-7dcc-4387-a7ca-4a69d37762c8","name":"lol-completed-matches-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
* upcoming - the match is scheduled for the future\n* live - at least one game in the match is being played right now\n* ended - the match has ended but we haven't settled all the markets available yet\n* completed - the match has ended and all the data is now available to settle all markets we offer\n* cancelled - the match being searched for doesn't exist
The rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\nNote this endpoint doesn't have a dates key like other sports because LOL leagues take place twice a year (summer and winter split). ie. all leagues listed take place from November to March and then from May to September.
\n","urlObject":{"protocol":"https","path":["raw","lol","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"d409200f-624e-409c-9b99-8886b764a1f8","name":"lol-league-mappings","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","lol","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"04915a0f-91e4-4ce9-a7a3-23f869a4d04e","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","lol","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"96cc96f3-e8ab-4c5d-9695-c2e1b8cce45a","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Worlds, All-Star Event, MSI, LCS, LEC, LCK, LCL, LJL, LCS Academy, Proving Grounds, PCS, LLA, VCS, TCL, CBLOL, LCO, European Masters. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: champion, level, kills, deaths, assists, totalGoldEarned, creepScore, killParticipation, championDamageShare, wardsPlaced, wardsDestroyed, attackDamage, abilityPower, criticalChance, attackSpeed, lifeSteal, armor, magicResistance, tenacity, currentHealth, maxHealth.
Team-Level Data: towers, dragons, totalGold, inhibitors, totalKills, game_length, result, barons
Query Parameters: date, matchid, time, team, league.
Table 3: Match Data
\nTable 3.1: Match Format Data
\nTable 3.2: League Details Data
\nTable 3.3: Team Data
\nTable 3.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","csgo","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"cda95d98-35de-4beb-8d04-98ff44322a87","name":"csgo-upcoming-matches-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for CS:GO. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","csgo","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"7d943c9d-01ff-4b70-a591-3c3163c6e282"},{"name":"Completed Matches","id":"682e4cd5-97b3-455d-aa52-51b57a819473","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 4: Match Data
\nTable 4.1: Match Format Data
\nTable 4.2: League Details Data
\nTable 4.3: Team Data
\nTable 4.3.1: Team Results Data
\nTable 4.3.2: Player Data
\nTable 4.3.2.1: Player Results Data
\n","urlObject":{"protocol":"https","path":["raw","csgo","completed-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a2784e72-e3eb-410c-9e99-a8d8ed955822","name":"csgo-completed-matches-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","csgo","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"30d5fc24-33cb-43fc-a71c-6d2da9dcbf5f","name":"csgo-league-mappings","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","csgo","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a29d9556-5c26-4109-a551-ec9437cf37b0","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","csgo","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"0e3c95d5-1bc3-4fb7-90cf-fd1a9a80e9d4","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: BLAST, Cologne, cs_summit, DreamHack, ELEAGUE, EMS, ESL, FACEIT, Flashpoint, Funspark, INTEL Extreme Masters, Katowice, MLG, Pinnacle Cup, PGL, Snow Sweet Snow, StarLadder, WePlay Academy League, World Electronic Sports, Championship, Major, Premier. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: kills, deaths, ADR, KAST , assists, flash_assists, headshots
Team-Level Data: rounds_won, total_Kills.
Query Parameters: date, matchid, time, team, league.
Note: For this endpoint, league_details.id, teams.id, and player.id are integers.
\nTable 5: Match Data
\nTable 5.1: Match Format Data
\nTable 5.2: League Details Data
\nTable 5.3: Team Data
\nTable 5.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","dota2","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"ac682345-e2d0-49e9-b6ce-3b6aa9102f43","name":"dota2-upcoming-matches-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Dota2. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","dota2","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[],"_postman_id":"c97fee91-f279-4d5c-9a2e-89f5ec0586d1"},{"name":"Completed Matches","id":"71330d92-09a0-4ba1-90a6-a05aafb706f2","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://rimbleanalytics.com/raw/dota2/completed-matches/","description":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Note: For this endpoint, league_details.id, teams.id, and player.id are integers.
\nTable 6: Match Data
\nTable 6.1: Match Format Data
\nTable 6.2: League Details Data
\nTable 6.3: Team Data
\nTable 6.3.1: Team Results Data
\nTable 6.3.2: Player Data
\nTable 6.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","dota2","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"f6ff5ec0-f1eb-4943-80f6-30787210f401","name":"dota2-league-mappings","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","dota2","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a4eb1134-62ef-4d6d-aeaf-7758f5c32c7d","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","dota2","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"e8c663ee-1e36-4741-b558-f35c73560d95","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Spring Regional League, Spring Major, Spring Regional Finals, Winter Regional League, Winter Major, Winter Regional Finals, Regional Qualifiers, The International, with 100+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: hero, kills, deaths, assists, level, leaver_status, last_hits, denies , gold_per_min, xp_per_min, net_worth, aghanims_scepter, aghanims_shard, moonshard , hero_damage, tower_damage, hero_healing, gold, gold_spent, ancient_kills, creeps_stacked, firstblood_claimed, lane_role, neutral_kills, observers_placed, roshan_kills, runes, sen_placed, towers_killed
Team-Level Data: score, ancient_kills, roshan_kills, result, towers
Query Parameters: date, matchid, time, team, league.
Table 7: Match Data
\nTable 7.1: Match Format Data
\nTable 7.2: League Details Data
\nTable 7.3: Team Data
\nTable 7.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","valorant","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"f199adb0-279b-4540-a12d-a9745f6f9a6d","name":"valorant-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","valorant","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"40d8a47c-b4c6-4a26-b174-face342fcec9","name":"valorant-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 8: Match Data
\nTable 8.1: Match Format Data
\nTable 8.2: League Details Data
\nTable 8.3: Team Data
\nTable 8.3.1: Team Results Data
\nTable 8.3.2: Player Data
\nTable 8.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","valorant","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"c92afe62-7934-4d0d-a319-916c0f9a82cd","name":"valorant-league-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","valorant","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"03362791-0d2b-4e1c-addd-c5f01f38ff32","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","valorant","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"f67d7111-cf78-4f48-9220-500221996538","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Challengers, Game Changers, Last Change Qualifiers, Masters, Champions, with 50+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data:first_kill, first_death, economy, acs, headshots, kast, s_defused, s_planted
Team-Level Data: t_score, ct_score, ot_score, rounds_won
Query Parameters: date, matchid, time, team, league.
Table 10: Match Data
\nTable 10.1: Match Format Data
\nTable 10.2: League Details Data
\nTable 10.3: Team Data
\nTable 10.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","rocketleague","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"c5ab0399-dd3d-4ce2-aafa-7f22a2d54845","name":"rocketleague-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","rocketleague","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a72728a3-135f-4e04-86ba-7ad80b33e881","name":"rocketleague-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 11: Match Data
\nTable 11.1: Match Format Data
\nTable 11.2: League Details Data
\nTable 11.3: Team Data
\nTable 11.3.1: Team Results Data
\nTable 11.3.2: Player Data
\nTable 11.3.2.1: Player Results Data
\n","urlObject":{"protocol":"https","path":["raw","rocketleague","completed-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"db7597f3-7dd0-4ba7-a4fc-55fe373c58d3","name":"rocketleague-completed-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","rocketleague","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"885a8374-0ef2-40d1-b30a-b27c73878576","name":"rocketleague-league-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","rocketleague","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"1fdd0104-aa9f-49bb-9a24-c4a5681c732e","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","rocketleague","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"7e5c32ca-11ad-451a-903f-87a7993eeaaf","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: RSC, RLCS, WCB, Masters, Champions, with 100+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: assists, goalParticipation, saves, total_distance, shots, shooting_percentage, goals, score
Team-Level Data: result, score, saves, assists, shots, goals, shootingPercentage
Query Parameters: date, matchid, time, team, league.
Table 12: Match Data
\nTable 12.1: Match Format Data
\nTable 12.2: League Details Data
\nTable 12.3: Team Data
\nTable 12.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","cod","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"807260fd-e9ab-4c3e-995d-1573d9fda583","name":"cod-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","cod","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a603d2ac-8109-4f19-875e-2fe7e6b4c815","name":"cod-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 13: Match Data
\nTable 13.1: Match Format Data
\nTable 13.2: League Details Data
\nTable 13.3: Team Data
\nTable 14.3.1: Team Results Data
\nTable 13.3.2: Player Data
\nTable 13.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Table 13.4: Stream Links Data
\n","urlObject":{"protocol":"https","path":["raw","cod","completed-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"bd54cca2-1940-43ae-bf5d-7e027c20f3f9","name":"cod-completed-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 15: League Data
\n","urlObject":{"protocol":"https","path":["raw","cod","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"249ee0e6-42e4-44d0-84c4-85af33285aea","name":"cod-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","cod","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"29011fa0-2992-4c45-9cc5-0e7ea7bdb76a","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","cod","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"48de00c0-a73c-45da-86ca-de6a0dd8284d","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Challengers, Major, Ultra Major, Qualifiers, Masters, Champions, with 50+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: kills, deaths, assists, bombs_planted, ctl_attack_rounds, ctl_bp_rating, ctl_defense_rounds, damage, defuse_count, first_blood_count, first_death_count, gametime_min, gametime_sec, hp_bp_rating, map_name, non_traded_kills, one_v_four_win_count, one_v_one_win_count, one_v_three_win_count, one_v_two_win_count, overall_bp_rating, plant_count, snd_bp_rating, snd_rounds,snipe_count
Team-Level Data: score , win_result
Query Parameters: date, matchid, time, team, league.
Table 13: Match Data
\nTable 13.1: Match Format Data
\nTable 13.2: League Details Data
\nTable 13.3: Team Data
\nTable 13.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","nba2k","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"e1b74c69-b729-443f-b199-8ce7f3467099","name":"nba2k-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","nba2k","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"43a567b8-43c0-4afb-a8fd-a9bffd8a81fe","name":"nba2k-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 14: Match Data
\nTable 14.1: Match Format Data
\nTable 14.2: League Details Data
\nTable 14.3: Team Data
\nTable 14.3.1: Team Results Data
\nTable 8.3.2: Player Data
\nTable 14.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","nba2k","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"2cff2400-e579-4020-a9eb-348f0d8303f5","name":"nba2k-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","nba2k","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"dd7c895e-ce75-4217-aabb-33fcc79adf93","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","nba2k","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"dbd5d3c9-3513-44a4-be9a-e01da6249bea","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Challengers, Qualifiers, Masters, Champions, with 50+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: position,player_id,vcp_id,number,offensive_rebounds,defensive_rebounds,total_rebounds,personal_fouls,fast_break_points,fast_break_points_made,fast_break_points_attempted,points_in_paint,points_in_paint_made,points_in_paint_attempted,points_per_elbow_touch,catch_shoot_points_made,catch_shoot_points_attempted,time_played,aopp,mopp,aopr,mopr,takeo,charges_drawn,boxouts,loose_balls_recovered,bdef,contested_2pt_shots,contested_3pt_shots,screen_assists,secondary_assists,passes_made,passes_received,passes_attempted,contested_offensive_rebounds,contested_defensive_rebounds,contested_rebounds,rebound_chances,vearly,early,searly, excel,vlate,late,slate,drblm,dbmpt,paint_touch,front_court_touches.
Team-Level Data: rebounds, assists, steals, blocks, personal_fouls, turnovers, field_goals_made, field_goals_attempted, 3_point_field_goals_made, 3_point_field_goals_attempted, free_throws_made, free_throws_attempted, offensive_rebounds, defensive_rebounds, total_rebounds, fast_break_points, fast_break_points_made,fast_break_points_attempted,points_in_paint,points_in_paint_made,points_in_paint_attempted,points_per_elbow_touch,catch_shoot_points_made,catch_shoot_points_attempted,time_played,charges_drawn,boxouts,loose_balls_recovered,bdef,contested_2pt_shots,contested_3pt_shots,screen_assists,secondary_assists,passes_made,passes_received,passes_attempted,contested_offensive_rebounds,contested_defensive_rebounds,contested_rebounds,rebound_chances, paint_touch,front_court_touches
Query Parameters: date, matchid, time, team, league.
Table 7: Match Data
\nTable 7.1: Match Format Data
\nTable 7.2: League Details Data
\nTable 7.3: Team Data
\nTable 7.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","fifa","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"15a218c3-1e39-4d57-a918-63eb94164fba","name":"fifa-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","fifa","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"d5c572ce-c28a-4fa7-8360-89155511a9c6","name":"fifa-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 8: Match Data
\nTable 8.1: Match Format Data
\nTable 8.2: League Details Data
\nTable 8.3: Team Data
\nTable 8.3.1: Team Results Data
\nTable 8.3.2: Player Data
\nTable 8.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","fifa","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"4f7a419a-8160-4612-946f-386fbb861bb6","name":"fifa-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","fifa","teams",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a01bdd8d-ad36-4ae5-914c-0e156ec4b1bc","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","fifa","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"f7435cee-1e60-418e-b83b-cfd30b2a8a56","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Club, Nations, World Cup, Continental, with 50+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: shootsOnTarget,shoots,possession,passingAccuracy,shootingAccuracy,duels,fouls,corners,yellowCards,redCards,injuries,offsides,goals,expectedGoals,interceptedBalls
Team-Level Data: N/A (team is same as player for FIFA).
\n","_postman_id":"40364e7d-a959-4df9-80e9-97279575adbb"},{"name":"Siege","item":[{"name":"Upcoming Matches","id":"759a4a65-4248-4bf1-81d0-f38a7c72e2cd","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"apikey","apikey":{"basicConfig":[{"key":"key","value":"x-api-key"},{"key":"value","value":"Query Parameters: date, matchid, time, team, league.
Table 7: Match Data
\nTable 7.1: Match Format Data
\nTable 7.2: League Details Data
\nTable 7.3: Team Data
\nTable 7.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","siege","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"94b6368c-fd66-415c-a8e7-5d8f9cdb8438","name":"siege-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","siege","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"a996560f-bbc1-46d7-b8a0-abd0aea4f79b","name":"siege-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 8: Match Data
\nTable 8.1: Match Format Data
\nTable 8.2: League Details Data
\nTable 8.3: Team Data
\nTable 8.3.1: Team Results Data
\nTable 8.3.2: Player Data
\nTable 8.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","siege","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"1eea8c54-cd04-40f4-a2a6-09fceb0c1691","name":"siege-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","siege","teams",""],"host":["rimbleanalytics","com"],"query":[{"disabled":true,"key":null,"value":""}],"variable":[]}},"response":[{"id":"b6a67cb7-e590-40e1-85f3-d10cf88d4908","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","siege","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"18e5a7a9-4cdf-4136-b6d0-451f19a9f62d","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Challengers, Game Changers, Last Change Qualifiers, Masters, Champions, with 50+ more smaller tournaments. We can also provide access to other smaller tournaments based on your requests.
Player-Level Data: kills, deaths, clutches, disables, explosive_kills, headshots, kost, opening_kills, plants, attacking_operator, defending_operator, service_requests, rating
Team-Level Data: map_name, score, win_result
Query Parameters: date, matchid, time, team, league.
Table 7: Match Data
\nTable 7.1: Match Format Data
\nTable 7.2: League Details Data
\nTable 7.3: Team Data
\nTable 7.3.1: Player Data
\n","urlObject":{"protocol":"https","path":["raw","cricket","upcoming-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"4c80e4b9-1e41-489a-936e-128907beeac9","name":"siege-upcoming-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
The format for this endpoint is exactly the same as upcoming matches for Valorant. We provide this endpoint to help you distinguish between matches that have gone live (and have therefore been taken off of upcoming matches) and matches that have been cancelled.
\nIMPORTANT NOTE: This endpoint was created to allow you to track matches that are live rather than to give you access to live data about matches. As such, this endpoint is the same as the upcoming matches endpoint, but it returns matches that are live instead of upcoming. To get access to live data about matches (like the latest team scores and player statistics), reach out to us at support@rimble.io - we use websocket connections to provide this data.
\n","urlObject":{"protocol":"https","path":["raw","cricket","live-matches",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"d2606efc-152e-44f6-b2d9-b4b18e83c498","name":"cricket-live-matches","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: date, matchid, time, team, league.
NOTE: We return completed matches for 5 days after their completion. If you require access to older matches, you may reach out to us directly.
Table 8: Match Data
\nTable 8.1: Match Format Data
\nTable 8.2: League Details Data
\nTable 8.3: Team Data
\nTable 8.3.1: Team Results Data
\nTable 8.3.2: Player Data
\nTable 8.3.2.1: Player Results Data
\nNOTE: A player may be on the lineup, but not on the starting team for all the games of the match. For example, a player might have only started for 2 out of the 3 games in a match. In those cases, we still have a player game results dictionary as described in the above table, but the values for the attributes are null's.
Query Parameters: matchid (required), date (required if match is older than 14 days).
This endpoint is added to provide you with a persistent endpoint to access the match status for any match. The format of this endpoint is a list of a single dictionary that represents the match you are searching for. This dictionary always has a match_status key that can have values:
upcoming - the match is scheduled for the futurelive - at least one game in the match is being played right nowended - the match has ended but we haven't settled all the markets available yetcompleted - the match has ended and all the data is now available to settle all markets we offercancelled - the match being searched for doesn't existThe rest of the dictionary format will follow the other endpoints we have described above (i.e. if the match_status is completed or ended, the match dictionary will have all the information described in \"Completed Matches\" endpoint).
Query Parameters: league_id, name, min_prize_money.
This endpoint gives you access to the most up to date mappings we have for leagues in Valorant. We return a league/tournament dictionary that has the information described in Table 9.
\nTable 9: League Data
\n","urlObject":{"protocol":"https","path":["raw","cricket","league-mappings",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"bad33ded-1409-45ce-865a-8aab978f68c5","name":"cricket-mappings-raw","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with team information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant team information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","cricket","teams",""],"host":["rimbleanalytics","com"],"query":[{"disabled":true,"key":null,"value":""}],"variable":[]}},"response":[{"id":"b157b223-e0fc-47f7-b7e0-c98c2eb8f1f2","name":"Teams","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Query Parameters: id (optional)
This endpoint is added to provide you with the ability to bulk update your local tables with player information.
\nNote this endpoint is not actively maintained but provides a starting point with relevant player information to make operations easier and player usernames might change for a given id over time.
\n","urlObject":{"protocol":"https","path":["raw","cricket","players",""],"host":["rimbleanalytics","com"],"query":[],"variable":[]}},"response":[{"id":"833f6ed5-7109-4f3d-be17-8ceb0c04a238","name":"Players","originalRequest":{"method":"GET","header":[{"key":"x-api-key","value":"Tournaments Supported: Ford Trophy, Champions Trophy, CSA Division Two, Logan Cup, WPL, etc. We can also provide access to other tournaments based on your requests. We cover all Men's T20, ODI, and Test as well as Women's T20.
Player Projections Supported: runs, wickets, strikerate, fours, sixes, economy, runs, wickets, strikerate, fours, sixes, economy
Team Projections Supported: runs, slug, balls, balls_per_over, byes, catches, catches_dropped, extras, game_number, innings, lead, legbyes, noballs, overs, penalties, runs, runs_saved, sixes, status, total_balls, total_overs, wickets, wides