🔁
Differences Between API 2 and API 3
At this page you will find the differences between API 2.0 and API 3.0.
Keep in mind there is a 'What is new?-page' as well to find out what is new.

Updated syntax

;can be used for adding multiple includes. For example, you want the stats of a certain season. In this case you would use participant;events
: can be used for filtering the fields you want to see in the response. For example, you only want the name of a certain team. You need to use participant:name
Alright, but I want more than the name of a team.
, can be used for adding another field to an include. For example, you want the teamname and gender of that team. You will use participant:name,gender

States and types

We introduced states and types to ensure data quality and consistency for specific fields.
For example, states for fixtures.
Position ID and detailed position ID are new types. Also, markets, periods, sidelined, referees, events, standings, metadata, formation, colours, injuries, suspensions, predictions, and stats.

Rate limit per entity versus per endpoint

The rate limit will now be based on requests per entity instead of being based on a single endpoint. For example, the teams entity is used in multiple Teams endpoints. You can find out more about the rate limit here.

Strict typing

Strictly typed languages enforce typing on all data being interacted with. For example int i = 3 string s = "4". In our API all fields are typed the same way.
Changelog updates after the Beta will be documented in the changelog.

Core and odds

Core and odds are no longer sport specific. Both have their own documentation now and are related to all sports that will be released on API 3.0.
Copy link
Outline
Updated syntax
States and types
Rate limit per entity versus per endpoint
Strict typing
Core and odds