Abios API

The Abios API Developer Hub

Welcome to the Abios API developer hub. You'll find comprehensive guides and documentation to help you start working with the Abios API as quickly as possible, as well as support if you get stuck. Let's jump right in!

NEW! You can find your personal developer dashboard and request log at https://dash.abiosgaming.com.

Teams, Players & Rosters

These are the guys putting their hearts and souls into the game

As you may imagine our database if absolutely filled with Teams and Players, and the way they connect to Matches may seem intuitive at first. Either a Player competes against another Player or a Team against another Team (with Players competing together). But it is unfortunately not that simple, in Games like Super Smash Bros two Players regularly play together against two other Players without necessarily playing for the same Team. This is where our Rosters come in to play, Rosters are groups of one or more Teams and/or one or more Players, lets look at them a little closer. As a last note before looking at each resources a little closer, Teams and Players have non-colliding ids which makes working with them a little simpler in some instances.

Players

There are not a lot of surprises with regards to Player data, we have data points such as nick name, nationality, team affiliation etc.

{
  "nick_name": "Armada",
  "deleted_at": null,
  "id": 6249,
  "first_name": "Adam",
  "last_name": "Lindgren",
  "images": {},
  "team": {},
  "country": {},
  "race": {},
  "stats": {},
  "previous_rosters": [],
  "game": {}
}

Teams

Teams are also quite straight forward and look like this:

{
    "id": 876,
    "name": "Ninjas In Pyjamas",
    "short_name": "NiP",
    "deleted_at": null,
    "images": {},
    "country": {},
    "stats": {},
    "rosters": [DefaultRoster], 
    "game": {}
}

Rosters

Rosters in the other hand are a little more abstract. As mentioned earlier there are different formats in which Teams and Players can combine themselves in when competing in a Match. Rosters are our representation of those formats. It might be a little more cumbersome to implement than Teams or Players being connected directly to a Match, but once implemented correctly Rosters are very versatile and handle all participation formats across Games! Here is what a Roster looks like:

{
    "id": 3456,
    "teams": [Team],
    "players": [Player]
}

The resource itself is fairly straight forward, one id and two lists containing Teams and Players respectively. Each such unique combination och Teams and Players form a Roster with its own unique id. Match history and performance can therefore be tracked based on each such unique set of teams and/or players. This makes our statistics very accurate!


What's Next

How to get all data grouped correctly across rosters in a Series

Seeding & Rosters