Getting Started

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 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.

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.