> 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/motorsport-api/tutorials-and-guides/tutorials/introduction.md).

# Introduction

This section covers everything you need to get up and running with the Motorsport API v3. Work through these pages in order if you are new to the API. If you are migrating from the Formula One API v1, start with the [Migration Guide](https://docs.sportmonks.com/v3/motorsport-api/tutorials-and-guides/guides/migrating-from-formula-one-api-v1-to-motorsport-api-v3) instead.

### In this section

* **Authentication** - How to generate your API token and attach it to requests.
* **Make your first request** - A step-by-step walkthrough of your first live API call.
* **Pagination** - How to page through large result sets using cursor-based pagination.
* **Set your time zone** - How `starting_at` timestamps work and how to convert them to a local time zone.

### Before you start

You need a Sportmonks account and an active Motorsport API subscription. Sign up at [my.sportmonks.com/register](https://my.sportmonks.com/register). Your API token is generated immediately and is available under **API > Tokens** in your dashboard.

The base URL for all Motorsport API v3 requests is:

```http
https://api.sportmonks.com/v3/motorsport
```

Every request must include your `api_token`. You can attach it as a query parameter:

```http
https://api.sportmonks.com/v3/motorsport/fixtures?api_token=YOUR_TOKEN
```

Or as an `Authorization` request header:

```
Authorization: YOUR_TOKEN
```

Both approaches are covered in full on the Authentication page.

### Related

* [Getting Started](https://claude.ai/welcome/getting-started)
* [Request options](https://claude.ai/welcome/request-options)
* [Endpoints](https://claude.ai/endpoints-and-entities/endpoints)
* [Entities](https://claude.ai/endpoints-and-entities/entities)


---

# 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/motorsport-api/tutorials-and-guides/tutorials/introduction.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.