> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/content/content-update-1/managing-images.md).

# Managing images

Enterprise connectivity allows the management of images via Content Manager or in the MultimediaObjects element within XML message.

### Content manager <a href="#managingimages-contentmanager" id="managingimages-contentmanager"></a>

All property images and image related data such as captions and image names are maintained and supported via Content Manager . Suppliers have the option to manage their Images via Content Manager. This User Interface allows easy access to add, update, or delete images and image Meta data.

### HCD XML update interface <a href="#managingimages-hcdxmlupdateinterface" id="managingimages-hcdxmlupdateinterface"></a>

Suppliers can provide the Image Meta data within the MultimediaObjects element of the XML Update Interface message along with the other descriptive content. The MultimediaObjects element includes: image file name, image caption text, image category (OTA codes), content ID, display order.


---

# 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://developer.rategain.com/content/content-update-1/managing-images.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.