> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/itservices/introduction/getting-started.md).

# Getting Started

<figure><picture><source srcset="/files/OxnQms7v4tIY75GPoqgV" media="(prefers-color-scheme: dark)"><img src="/files/g1jtoO4Od8ow4hv1fofK" alt=""></picture><figcaption></figcaption></figure>

Insight Tech Services is designed to be API-first and fast to integrate. Whether you're embedding model outputs into your backend systems or exploring the data through the Insight Tech Console, this guide will help you take the first steps.

In both cases (UI or API) having a working ticket integration (either `ticket-placement` or `ticket-inform`) is a hard prerequisite for receiving any data or model output from Insight Tech Services. Without a steady stream of ticket data, the platform cannot generate insights or populate dashboards.

To learn more, visit the [Transaction 3.0 API](https://docs.sportradar.com/transaction30api/) section.

### Provisioning and access

Before accessing Insight Tech Services, it is essential to ensure that your system is integrated with Sportradar’s ticketing infrastructure. Depending on your operational model, this can be achieved through:

* Ticket placement (`ticket-placement`): Used by fully risk-managed clients via MTS, where Sportradar performs all validation.
* Ticket inform (`ticket-inform`): Used by clients who validate tickets on their own infrastructure and send them to Sportradar for analytics purposes. This is the most common method used with Insight Tech Services.

The chosen method of integration (whether `ticket-placement` or `ticket-inform`) must be operational before Insight Tech Services can process and analyse your transactional data. This applies to both the UI and API-based use cases.&#x20;

### What’s next?

Once you’ve authenticated, you're ready to call your first model.

* Explore available models in the Model Catalogue
* Review the API Integration Guide for endpoint structure and usage
* Learn how to use the Insight Tech Console if you prefer a no-code interface

If you have any questions during onboarding, your Operational Account Manager or Service Delivery Manager is available to support you.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/itservices/introduction/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.