πŸ™‹β€β™‚οΈGetting Started

We'll briefly inform you about the features of our API, and then you can explore our documentation for yourself. You will also find out how to create your dream application. Sportmonks offers standard REST APIs. Requests are sent with URLs and responses will be returned in JSON format. Every authentication is spearheaded by an API token. We have assembled a library of all of our endpoints including example requests in Postman.

circle-info

We also offer detailed postman documentation with examples and a complete up-to-date version of all our endpoints. Below is a button that lets your fork the collection or import it

Run in Postmanarrow-up-right

Short introduction to Sportmonks:

Now you know who we are, what we do, what we offer, and how we can help you: We suppose you want to get started right away. Head over to our Getting Started section, where you'll create your own API token and create your first request

What else do we cover in the documentation?

API structure

Persona-based getting started paths

Different developers have different needs and experience levels. This document provides tailored getting started paths for each user persona, helping them find the most relevant documentation quickly and reducing time-to-first-success.

Choose your path

Select the path that best describes you to get started quickly with the right resources:

New to APIs?

You're here to: Learn what APIs are and how to use Sportmonks for the first time.

Your learning path

Step 1: Understand the basics

Step 2: Get set up

Step 3: Learn core concepts (15 min)

Step 4: Build something simple (10-15 min)

Experienced developer, new to Sportmonks?

You're here to: Get productive quickly with Sportmonks' most powerful features.

Your fast-track path

Step 1: Quick setup

Step 2: Power features

Step 3: Essential tutorials

Step 4: Optimise

Pro tips:

Migrating from API v2?

You're here to: Upgrade from API v2 to v3 smoothly and quickly.

Your migration path

Step 1: Understand changes (10 min)

Step 2: Breaking changes checklist

  • Participants replace localTeam/visitorTeam - Update team includes

  • New include syntax - Use semicolons (;) instead of commas

  • New pagination - No more total_pages in response

  • Rate limits per entity - Not per endpoint anymore

  • Statistics only show recorded values - No default zeros

  • Trends structure changed - New period-based format

  • Bookmaker IDs changed - Use legacy_id for mapping

Step 3: New features to explore

Migration checklist:

Building specific applications?

Choose your application type for a focused guide:

Livescore app

What you'll build: Real-time match tracker with scores, events, and lineups.

Your path

  1. Core features

  2. Enhancement features (15 min)

  3. Optimisation

  4. Polish

πŸ“± Quick Implementation:

Betting platform

What you'll build: Platform with odds, predictions, and statistics.

Your path:

  1. Foundation

  2. Odds & predictions

  3. Advanced stats

  4. Implementation

Fantasy football

What you'll build: Fantasy league with player stats and scoring.

Your path

  1. Player data

  2. Scoring system

  3. League management

  4. Advanced features

Sample fantasy points calculation:

Stats dashboard

What you'll build: Analytics dashboard with trends, comparisons, and visualizations.

Your path

  1. Advanced metrics

  2. Comparisons

  3. Visualisation tips

Dashboard components:

  • Team form chart (last 10 matches)

  • xG vs actual goals scatter plot

  • Player comparison radar charts

  • League-wide statistics tables

  • Trend lines for key metrics

Additional resources by persona

For beginners

Helpful Guides:

For experienced developers

Advanced topics:

Performance:

For migrators

Migration tools:

Need help?

Can't find what you're looking for? We're here to help:

Quick help

Direct Support

Report Issues

See also

Last updated

Was this helpful?