> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/welcome/most-important-docs-pages.md).

# Most important docs pages

Whether you're just getting started or refining your integration, these are the pages you’ll use most. Bookmark them, explore them, and make the most of your Sportmonks journey.

#### 🧭 Introduction tutorial

**Kickstart your Sportmonks experience.**\
New to our API? Start here. Learn how authentication works, how endpoints are structured, and how to make your first successful request. Step-by-step guidance helps you move from your first call to confident querying.

> 🎯 *Perfect for developers integrating Sportmonks for the first time.*

[Go to Introduction Tutorial →](https://docs.sportmonks.com/football/tutorials-and-guides/tutorials/introduction)

#### 🔧 Request Options

**Shape your data, your way.**\
Master the art of efficient requests. Learn how to filter, sort, paginate, and include related data without unnecessary overhead. Build smaller, faster, and more precise responses.

> ⚙️ *Essential for performance-focused applications.*

[Explore Request Options →](https://docs.sportmonks.com/football/api/request-options)

#### 📁 Demo Response Files

**See it before you build it.**\
Preview actual JSON responses for fixtures, teams, players, and standings. These files are ideal for planning data models, front-end components, or testing integrations before going live.

> 🧩 *Useful for developers designing data structures and prototypes.*

[View Demo Files →](mailto:undefined)

#### ✅ Best Practices

**Build smarter and scale confidently.**\
Avoid common pitfalls with expert guidance on topics like caching, rate-limiting, timezone handling, and database synchronisation. These principles ensure your integration remains stable and efficient as you grow.

> 🛠 *Highly recommended for production setups.*

[Read Best Practices →](https://docs.sportmonks.com/football/welcome/best-practices)

#### 📚 Guides Collection (incl. Components Guide)

**Go beyond the basics.**\
Explore structured tutorials packed with real examples. Learn how to build modular and reusable data structures with the Components system, and how to combine endpoints effectively.

> 📘 *For developers expanding from simple requests to advanced builds.*

[Browse Guides →](https://docs.sportmonks.com/football/tutorials-and-guides/guides/how-to-use-components)

#### 🔄 States

**Track every match’s lifecycle.**\
Understand how fixture states define the timeline of a match — scheduled, live, halftime, finished, or cancelled. Use them to power live dashboards and notifications with real-time accuracy.

> ⏱ *Key for live-score and timeline applications.*

[Learn about States →](https://docs.sportmonks.com/football/definitions/states)

#### ⚡ Events

**Follow every key moment.**\
Events capture the action: goals, cards, substitutions, and more. Learn how to include and interpret them to build detailed match feeds, commentary systems, and visual timelines.

> 🎯 *Ideal for match trackers and live commentary widgets.*

[Read Events Docs →](mailto:undefined)

#### 📊 Statistics

**Turn data into insight.**\
Dive deep into performance metrics like shots, passes, possession, and expected goals. Use this data to fuel analytics dashboards, fantasy scoring, and predictive models.

> 📈 *Perfect for analytics, scouting, and performance tools.*

[Explore Statistics →](https://docs.sportmonks.com/football/definitions/types/statistics)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportmonks.com/v3/welcome/most-important-docs-pages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.