> 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/ads/ad-s-marketing-cloud-api/api-overview.md).

# API Overview

The API enables the user to connect directly to the back-end of the Reporting Studio, allowing you to pull DSP data into your back-end to enable self-service reporting capabilities.

### **Requesting Access**

To request access please follow [this link](https://docs.sportradar.com/ads/ad-s-marketing-cloud-api/how-to-access-the-api.md).

### **Reporting Studio Setup**

| **Filters**    | Limit the data in your report. For example, add the Advertiser filter, and your report will only contain about the chosen advertiser.                         |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dimensions** | Descriptors that aren't numerical totals like clocks or impressions. For example, choose Creative ID to report on how a given type of creative is performing. |
| **Metrics**    | Units of measurements like clicks, conversions or impressions. They are often expressed as numerical totals or percentages.                                   |

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

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

```
GET https://docs.sportradar.com/ads/ad-s-marketing-cloud-api/api-overview.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.
