Integration

How do I integrate Livescores?

Currently, our API provides only a pull mechanism. That means that if you want to check for changes, you'll need to make requests. For livescores, most customers have found it best to check in every 1-2 seconds to get the latest data. That way, you'll ensure your livescore app has an accurate maximum delay of around 2 seconds. Plus, our scouts are on top of it; they watch the game live, and enter the data as soon as it happens on the field.

How do deleted and postponed fixtures work?

Deleted fixtures will not be updated; they have been received incorrectly. Postponed fixtures retain the same fixture ID and are updated when the start time/date changes.

How do placeholders work?

We created placeholder teams. Once it is known which team belongs to which spot > the teams will change into the correct team. For example, the placeholder ID will then change to the ID of Brazil because we then know Brazil is the team that claimed that spot. Right now, we cannot know which team will end up at which spot. We have created these placeholder IDs so you can see that the winner of Group X will play versus the 2nd of Group Y. You can find a full tutorial on how placeholders work on this page:

Placeholders

How does our rate-limiter work?

Our rate limiter works as follows;

• Every default plan has 3000 API calls per entity per hour.

• If you hit your rate limit, for example, on the livescores entity, you can still request the teams entity.

• The rate limit resets an hour after your first request for that entity was made.

How does pagination work?

The pagination mechanism in API 3.0 differs from our current API version. Instead of providing total page counts, it utilizes a cursor for navigating to the next page. This structural change significantly enhances API performance. For additional details, please refer to our dedicated page:

Pagination

How do I track my usage?

You can track your usage in our user-friendly My.Sportmonks environment or using this endpoint:

GET My UsageCore API 3.0

The other alternative to find the usage is by scrolling to the bottom of your API call and you will see the rate limit details for the entity queried. Here's an example:

"rate_limit": {
        "resets_in_seconds": 3600,
        "remaining": 2999,
        "requested_entity": "Topscorer"