🆕Differences between API 2 and API 3

Introduction

We've made various changes to our new API. These changes result in some groundbreaking differences between API 2 and API 3. This section of the documentation is here to help you understand how to adopt all the latest changes, improve the quality of your applications and streamline your development experience. Here's a quick overview of some differences between API 2 and API 3.0:

• API changes

  • States and types

  • Strict typing

  • Include changes

  • Rate limit per entity

• Syntax, extensive filtering and select options

• New data features and endpoints

Checking the differences between two API versions can help you identify changes that may affect your code and make any necessary adjustments. Please don't hesitate to contact us with any questions or concerns.

To better serve our growing customer base and meet the demand for more sports-related services, we have introduced a new API: Sportmonks V3. This updated configuration is designed to deliver improved reliability, broader coverage, and a variety of new data features and endpoints that were simply not possible with API V2. You can find these enhancements here.

To maintain the highest possible data quality, the validation for V3 is stricter. Additionally, the entire structure of V3 is different compared to V2. As a result, data discrepancies may arise between V2 and V3. We strongly recommend using the newest version of our Football API (V3) to benefit from improved data quality. The data quality of V3 is way more reliable and accurate due to its new structure and the validation methods we use. Furthermore, future innovations will only be available on API 3.0, so we recommend switching as soon as possible.