---
title: "Updating a Content Store Element"
slug: "updating-a-content-store-element"
description: "Use case: look up the ID of a Content Store element and update its description and expiration setting with the Mapp Engage API."
status: "new"
updated: 2026-11-03T14:06:41Z
published: 2026-11-03T14:06:41Z
canonical: "docs.mapp.com/updating-a-content-store-element"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Updating a Content Store Element

Content Store elements hold files and HTML content that you use in emails and landing pages by their ID. This use case shows how to read an existing element and change its description and expiration setting through the Engage API, so you can maintain elements from your own systems.

## Prerequisites

Before you begin, make sure you have valid authorization credentials. See [Getting Started with Engage API](/v1-api/apidocs/getting-started-with-engage-api) for more information.

You need the ID of the element. To find it, go to Content > Content Store and click the element. The ID is shown in the Details section below the list. The API does not provide a way to search or list Content Store elements, so look up the ID in the Mapp Engage interface first.

## Procedure

Optionally, read the current state of the element with `GET /content/get`. Pass the ID in the query parameter `contentId`. The response contains the content and the metadata of the element.

Then update the element with `PUT /content/update` and pass the same ID in `contentId`. Send only the fields you want to change. Fields that you leave out of the request body stay unchanged. This example changes the description and the `expirationAutomatic` setting:

```json
PUT 'https://your-engage-domain.com/api/rest/content/update?contentId=1234'
{
  "description": "my new description",
  "expirationAutomatic": true
}
```

The response contains the updated element.

## Conclusion

An update does not change the ID of the element or the placeholders that point to it, so you do not need to edit the templates or messages that reference it. For the fields you can change, see the API reference pages below.

## Related Topics

[Read a content element](/v1-api/apidocs/read-a-content-element)

[Update a content element](/v1-api/apidocs/update-a-content-element)

[Content Store](https://docs.mapp.com/docs/en/content-store)

[Getting Started with Engage API](/v1-api/apidocs/getting-started-with-engage-api)