> 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/datacore/sports-apis/baseball/datacore-api-v1/introduction/images.md).

# Images

Some API calls will return image objects for things such as logos or photos. The url field of the image object contains the url where you will find that image. This url is for the 'default' version of the image. There are some query string parameters available to change how the image is returned.

`format`

By default the image is returned in whatever format it was uploaded in, but by specifying the 'format' parameter you can change this. Valid options are: `png`, `jpg`, `webp`.

`size`

By default the image is returned as a square of 100x100 pixels. By specifying the 'size' parameter the image will be returned at a difference size. The available options are

| size parameter | dimensions                                               |
| -------------- | -------------------------------------------------------- |
| `100`          | 100x100                                                  |
| `200`          | 200x200                                                  |
| `400`          | 400x400                                                  |
| `800`          | 800x800                                                  |
| `1000`         | 1000x1000                                                |
| `RAW`          | The original dimensions that the image was uploaded with |

Images will not be scaled up. If you ask for an image with `size=400`, but the image is only 200x200 then the image will be returned as 200x200.

All images returned (apart from `size=RAW`) are square. If the original image that is uploaded is not square, then it is padded with a transparent (white for jpg) background.

An example url is: `https://img.dc.atriumsports.com/586aa6b195d243c4ae4154c8a61eda19?size=200&format=webp`


---

# 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/datacore/sports-apis/baseball/datacore-api-v1/introduction/images.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.