ÃÛ¶¹ÊÓƵ

DocumentationAEM as a Cloud ServiceUser Guide

How to Update Your Content via AEM APIs update-your-content

Last update: Thu Mar 27 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
  • Developer

In this part of the AEM Headless Developer Journey, learn how to use the available APIs to access and update the content of your Content Fragments.

The Story So Far story-so-far

In the previous document of the AEM headless journey, How to Access Your Content via AEM Delivery APIs you learned how to access your headless content in AEM via the AEM GraphQL API and you should now:

  • Have a high-level understanding of GraphQL.
  • Understand how the AEM GraphQL API works.
  • Understand some practical sample queries.

This article builds on those fundamentals so you understand how to update your existing headless content in AEM via the available APIs.

Objective objective

  • Audience: Advanced
  • Objective: Learn about the APIs available to access and update the content of your Content Fragments.

AEM APIs for use with Content Fragments aem-apis-for-use-with-content-fragments

ÃÛ¶¹ÊÓƵ Experience Manager (AEM) as a Cloud Service offers multiple APIs for both structured content delivery from Content Fragments and Content Fragment management. See the individual pages for further details of the specific APIs.

  • AEM REST OpenAPI for Content Fragment Delivery

    • This API creates JSON responses for delivering structured content from Content Fragments in AEM.
    • It uses a path to a content fragment as endpoint.
    • This API is REST based.
    • It is optimized for content delivery, including CDN integration.

  • AEM GraphQL API for Content Fragment delivery

    • This API is schema-based. API schemas are represented by Content Fragment Models, which define the content structure.
    • This API is GraphQL based.

  • Content Fragments and Content Fragment Models OpenAPIs

    • These APIs are intended for structured content management.
    • Respective GET operators are not optimized for content delivery.
    • This API is REST based.

  • Content Fragments Support in the AEM Assets HTTP API

    • The original API for the JSON output for structured content delivery in AEM.
      • While robust and proven, this API does not deliver fully hydrated JSON output. References are only output as paths, requiring secondary API requests for retrieving further content.
    • The Assets HTTP API can also be used for managing the Content Fragments and Content Fragment Models (CRUD).
    • This API is REST based.
    • Content Fragment Support in Assets HTTP API will be deprecated in the future as it is being succeeded by the Edge Delivery Services JSON REST API. The timescale has not been decided yet.

What’s Next whats-next

Now that you have completed this part of the AEM Headless Developer Journey, you should:

  • Understand the AEM APIs available.
  • Understand how Content Fragments are supported in these APIs.

You should continue your AEM headless journey by next reviewing the document How to Put It All Together - Your App and Your Content in AEM Headless where you will get familiar with the AEM architecture basics and tools you need to use to put your application together.

Additional Resources additional-resources

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab