> 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/uof/premium-cricket/scoring-api.md).

# Scoring API

### API Overview <a href="#uofpcscoringapi-apioverview" id="uofpcscoringapi-apioverview"></a>

The Premium Cricket Scoring API is a simple web API designed to complement the odds content for the Premium Cricket product, which is consumed via the Betradar Unified Feed. Its main purpose is to provide bookmakers with data that can be used in event scheduling, and to provide a scoreboard display for customers during matches that are traded In Play as part of the Premium Cricket product

### Authentication <a href="#uofpcscoringapi-authentication" id="uofpcscoringapi-authentication"></a>

The `x-access-token` varies between Production and Staging environments. Access tokens should align with the specific environment being used. For example, if you are integrating on the staging environment, provide the staging access token and use the staging URLs accordingly.

**Note** - Please use your existing [Unified Odds Feed access token](/uof/api-and-structure/api.md) to authorize your API access.

### Self-service Documentation <a href="#uofpcscoringapi-self-servicedocumentation" id="uofpcscoringapi-self-servicedocumentation"></a>

All endpoints are available for testing purposes at <https://iodocs.betradar.com/>. From there, you can see each of the endpoints, execute the requests, and see sample responses as long as you have an access token.

### Change Process <a href="#uofpcscoringapi-changeprocess" id="uofpcscoringapi-changeprocess"></a>

Non-breaking changes (additions) to the API schema will be made without notice; therefore, integrations should be resilient to such additions. If a breaking change is required, we will version the API and maintain the old version for three months to allow time for migration to the new version.

<br>


---

# 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/uof/premium-cricket/scoring-api.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.