---
title: "Mapp Engage: Read and Update Content Store Elements via API"
slug: "mapp-engage-read-and-update-content-store-elements-via-api"
description: "Mapp Engage API: read and update existing Content Store elements by ID with the new GET and PUT operations, without changing templates."
status: "update"
updated: 2026-11-03T14:10:58Z
published: 2026-11-03T14:10:58Z
canonical: "docs.mapp.com/mapp-engage-read-and-update-content-store-elements-via-api"
---

> ## 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.

# Mapp Engage: Read and Update Content Store Elements via API

**3 November 2026** The Mapp Engage API now lets you read and update existing Content Store elements. Until now, the API only allowed you to create new elements and delete them.

## What's new

- **Read an element:** The new GET operation returns the current content and metadata of a Content Store element by its ID. See [Read a content element](https://docs.mapp.com/apidocs/en/read-a-content-element).
- **Update an element:** The new PUT operation updates an existing element in place by its ID. Fields that you leave out of the request stay unchanged. The element ID and the placeholders that point to the element do not change, so you do not need to edit the templates that reference it. See [Update a content element](https://docs.mapp.com/apidocs/en/update-a-content-element).

Integrations and automation tools can use these operations to maintain Content Store elements without manual work in the Mapp Engage interface. For a step-by-step example, including how to find the element ID, see [Updating a Content Store Element](https://docs.mapp.com/apidocs/en/updating-a-content-store-element).

## Availability

The new operations are available now in the Mapp Engage API. See the API reference pages above for parameters and the fields you can change.