Adobe Experience Manager Headless

Emirates Seat Selection: Complete Guide to Choosing Your Flight SeatEmirates Seat Selection allows travelers to choose a preferred seat before their flight, subject to availability and the conditions of their fare. Selecting a seat in advance can be useful for passengers who prefer a window or aisle seat, want to sit with companions, or are looking for additional space.Travelers can usually access seat-selection options through their Emirates booking and review the available seating choices for their flight. Depending on the ticket type, route, travel class, and selected seat, an additional charge may apply. Some passengers or fare types may receive complimentary seat-selection options.Emirates offers different seating locations, including window, aisle, and middle seats, while certain aircraft may also provide options with extra legroom or other preferred locations. Availability can vary according to the aircraft configuration and how early the seat is selected.To choose a seat, passe

i have created the configuration to enable persisted queries for my endpoint but when I am in the query editor, there is a message stating that they are not enabled. What could I be missing?

I have some content fragments defined in a project folder. I then went to the configuration manager and created a policy that enabled content fragments models in the configuration folder then also enabled GraphQL as well. I then applied that policy to my parent folder for assets, where I planned to create the content fragments. I was then unable to see my content fragment models when I tried to create a content fragment in that folder or child folders that were set to the default inheritance. When I moved my models to the global folder (I don’t think this should be the resolution) I could then see my defined models.I would prefer to do this correctly and use the content fragments in the project folder so they can be added to source control without affecting other configurations.What could be a reason that I am not able to see the project specific models, but I can if see the models in the global folder. Again, I followed the directions on creating a policy to allow the project models.

We're delivering Content Fragments headlessly via the AEM as a Cloud Service GraphQL API for a multi-market site. We already use `_locale` to fetch the right language version of our fragments, and it works great OOTB. What I'm trying to figure out: Is there an equivalent OOTB system parameter for country or market the way `_locale` exists for language? Something like a _country OR / _market argument I could pass into the query?Our content structure looks like  “/content/dam/<brand>/us/en/...”, “/content/dam/<brand>/uk/en/...”, etc. I know I could filter on `_path` with `STARTS_WITH`, but for this use case we'd prefer not to rely on path-based filtering.Question:1. Does AEM GraphQL expose any OOTB country/market parameter, or is “ _locale” the only geo-related system parameter?2. If there's nothing OOTB, what's the recommended way to model market so it filters cleanly in GraphQL?

I have an old quickstart from several years ago that didn’t include the GraphQL feature. I’d like to add it to my local copy so that I can do some personal discovery and testing. Is there a chance that there is a package I could download without having a business cloud account?

I am trying to build a custom widget for external links in a new content fragment editor RTE and store those values into an anchor tag. I have tried both the options to use getwidget and getcustombutton options, but looks like the getcustombutton options is deprecated. I am able to run the build with my custom code using getwidget function and don’t see any errors in the console logs. Also, I don’t see an option to view the pop-up using the curly brace option. Can someone help me with the limitations with extensibility options?

Curious how enterprise AEM Cloud teams are evolving Content Fragment modeling strategies as AI-driven personalization and multi-channel delivery become more common.Historically, many content models were designed primarily around page rendering and headless delivery needs. But with increasing AI-assisted content generation and dynamic experience orchestration, the modeling requirements seem to be changing rapidly.Interested in perspectives around:reusable fragment design metadata strategy AI-friendly taxonomy structures personalization scalability GraphQL performance considerations and governance for large content ecosystemsWould love to hear how teams are preparing their content architecture for more AI-driven experience delivery models.

The second part of a series is now published on Perficient’s website: Implementing Headless Page-based Authoring in Adobe’s Universal Editor. (The first article can be found at here.)Link to the article → https://blogs.perficient.com/implementing-headless-page-based-authoring-in-adobes-universal-editor-part-2/  

As generative AI and Retrieval-Augmented Generation (RAG) continue gaining traction across enterprise platforms, I’ve been thinking about how current AEM content architectures will need to evolve to support future AI use cases. Many AEM implementations were originally designed around page rendering, content reuse, and headless delivery. However, AI-driven experiences introduce additional requirements around content retrieval, context quality, metadata strategy, and knowledge organization. Some areas we’re currently evaluating include: • Content Fragment design and granularity• Metadata quality and governance• Taxonomy structures for improved retrieval accuracy• Structured vs unstructured content strategies• Content duplication and source-of-truth management• GraphQL delivery patterns for AI-powered applications• Preparing enterprise content repositories for future RAG architectures One challenge I see is that AI systems are only as effective as the content they’re able to retrieve and

Hello Adobe Team, currently modern image formats are not fully supported end-2-end.In the CF EditorAVIF = Asset reference can be selected, NO preview image shown to authors. The delivey through Dynamic Media with OpenAPI is workingJPG XL = Asset reference can be selected, NO preview image shown to Authors. The delivery through Dynamic Media with OpenAPI is NOT able to render it. Thanks,Tim

Hi all,we are registering API client ID’s in an api.yaml (see https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/open-api-based-apis) and deploy them with a config pipeline.The documentation describes that for secrets can be used placeholders (see https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/config-pipeline) Something like shown here seems not to work: kind: "API"version: "1"data: allowedClientIDs: author: - "${{MY_AUTHOR_CLIENT_ID}}"We added the values as secrets with “Service Applied: All” in cloud manager configuration but it only works with specific values directly in the api.yaml.Do you know if this not supported kind: API?Best,Mark

Hi all,I'm working on an AEM 6.5 project and need to serve Content Fragment data as a hierarchical JSON response grouped by subfolder, not just a flat list. Looking for advice on whether my approach is sound or if there's a better way.RequirementI have content organized in subfolders under a parent folder in the DAM. Each subfolder represents a "section" of a page, and each section contains multiple content fragments of the same model.DAM structure:/content/dam/.../parent-folder/  ├── section-alpha/  │   ├── item-1   (CF)  │   └── item-2   (CF)  ├── section-beta/  │   └── item-1   (CF)  ├── section-gamma/  │   └── item-1   (CF)  └── section-delta/      ├── item-1   (CF)      ├── item-2   (CF)      └── item-3   (CF)Expected JSON response (strict contract with frontend):{  "page_name": {    "section_alpha": {      "items": [        {          "field_a": "value",          "field_b": 2,          "field_c": ["tag1", "tag2"],          "field_d": "some expression",          "field_e": "Title

I have a situation where i need to make an AEM author post call from my OSGI Service, now we need some authentication to make this call , i tried with basic auth and it works absolutely fine. But i am looking for more secure option like by using bearer token and upon researching i found out we can use OAuth since JWT is deprecated. But after setting up OAuth i am getting 403 Forbidden from my api call response, earlier i used to get 401 unauthorized. Can someone suggest what should be the ideal setup for making AEM API calls using OAuth, it seems i have set it up incorrectly.

I have this ruleRewriteRule ^/content/my-project/([a-z]{2})/en/(.+)\.html$     /$1/$2 [R=301,L] Now when i hit with CDN domain then my CDN domain gets converted into AEM publish domain and this is true for all the 301 & 302 redirects. Followed couple of articles and did not worked like by adding {HTTP_HOST}, is any header needed in CDN to support this?

Hello everyone, I'm looking to migrate from an old, headful CMS to AEM Headless. The database of our current headful CMS is PostgreSQL 15, and the content is marked up with a proprietary template. We plan to distribute information to multiple devices, such as native apps and IoT devices, and therefore want to use GraphQL.Does anyone have information on how to migrate from a third-party CMS like this? I understand that the Content Transfer Tool (CTT) is for data migration between AEM instances, but what's the best practice for migrating data from another CMS?https://experienceleague.adobe.com/ja/docs/experience-manager-cloud-service/content/migration-journey/cloud-migration/content-transfer-tool/overview-content-transfer-tool Thanks.

Hi Everyone, How to provide a preview experience (or a WYSIWIG editor) for a native mobile app that uses AEM headless for content delivery? Content is authored on 'AEM sites' pages using core components that expose data as .model.json For an SPA or a web app, using the SPA editor or universal editor makes this possible. But how to approach this for a brand that has only native apps and no web presence?Please recommend any possible or recommended approaches that you might have encounteredThanks in advance!

I have a XF which is targeted using context hub and when i try to refer it via OTB Experience-Fragment component then everything works fine like its rendering the proper content and not full html in dom but when i do the same with custom xf reference component then its loading the full html in domI am using the same code as OTB to render the html and making sure my XF path is till /jcr:content since in OTB component also we load the path till /jcr:content. Also if i give a non targeted XF then everything works fine

Hi Everyone,We are currently developing sample components for the AEM Universal Editor. While editing works as expected on local using a local universal editor service, we are encountering issues on the Dev environment when switching to the Global Adobe-managed service endpoint.Specifically, we are seeing timeout and CORS errors related to the Universal Service, preventing the component from being configured. Since we are on AEM 6.5.23.we added all the domain in the cors policy configuration still we got the error.Has anyone successfully configured the global endpoint for AEM 6.5 ? Any insights would be appreciated.below is the tag added in the head.html<meta name="urn:adobe:aue:config:service" content="https://universal-editor-service.adobe.io"> ---pointing to globalfor local <meta name="urn:adobe:aue:config:service" content="https://localhost:8080"> ---pointing to local

I am using AEM 6.5 (Cloud SDK) with the old Content Fragment editor view.In my Content Fragment Model, I configured a Fragment Reference field with the following settings: Render As: Multiple Field Min Number of Items: 2 Max Number of Items: 4 However, when I create a Content Fragment based on this model, I am still able to: Add only 1 referenced fragment Save the Content Fragment successfully Max items works as expected The system does not block the save operation even though the minimum number of items is set to 2.My Questions: Is this expected behavior in AEM 6.5 (classic/old editor)? Are Min/Max item constraints only UI-level guidance and not server-side enforced? Is there any way to strictly enforce the minimum item count without custom development? Does this behavior differ in the new Content Fragment Editor or in AEM as a Cloud Service? I also checked CRXDE under:/conf/wknd/settings/dam/cfm/models/wknd-content-fragment-modelThe minItems property is correctly set, b

We have need to query GraphQL in AEM for specific content fragments with a title (for example) of X or Y. That’s easy enough to do with a query like this. This is the most common example I see.  query getAdventuresByActivity( $activity1: String! $activity2: String!) { adventureList(filter: { adventureActivity: { _logOp: OR _expressions: [ { value: $activity1 } { value: $activity2 } ] } }) { items { _path adventureTitle adventureActivity adventurePrice adventureTripLength } }} Then followed by a variable like this. { "activity1": "Surfing", "activity2": "Rock Climbing"}The issue is that we’d like to be able to query on n number of variables and there doesn’t seem to be a facility for this. You can pass in a dynamic filter expression to the persisted query, but this only works in Graphiql. I’m wondering what other folks out there are doing for a problem like this. Are you simply making multiple single filter calls t

HiI am getting this error on trying to instantiate new Document.I am using gradle with dependency com.adobe.aemfd:aemfd-client-sdk: 6.0.904I don’t see this class in the jar either. Is there any other dependency I should add to resolve this issue?Thanks!

in graphiql explorer, the query works normally: but in postman, I get this error: 

We have following persisted query: http://localhost:4502/graphql/execute.json/test-project/get-articles-by-path%3BstartsWith%3D%2Fcontent%2Fdam%2Ftest-project The GraphQL query has the parameter "startsWith" which takes a path like this:  query getArticlesByPath($startsWith: ID!) { articleCfmList(filter: { _path: { _expressions: [ { value: $startsWith _operator: STARTS_WITH }] } }) { items { ...   It works perfectly fine on author and publisher but when sending the same request to the dispatcher it will not send the request correctly to the publisher because the encoded path is not correctly transmitted.We have tried it with directive AllowEncodedSlashes NoDecodebut it didn't help. What is the correct dispatcher setting for these kind of parameters?

Hi community, I'm new to Adobe Experience Manager (AEM) and I'm particularly interested in learning about headless adaptive forms especially developing with JSON Schema instead of GraphQL.I don't yet have any AEM license, as I'd like to first understand and explore the platform before committing to a subscription.I've read that it's possible to set up AEM locally and also the AEM as a Cloud Service SDK, for development and learning purposes. However, I haven't been able to find clear instructions or a direct download link - most resources redirect me to the enterprise page, which says my Adobe ID isn't linked to a subscription.So, my questions are:How can a new developer (without an enterprise account) start learning and building on AEM?Is there any free developer sandbox or trial setup available for learning?What's the recommended learning path to get started with hands-on development, evaluate features, and build skills before subscribing?Thanks in advance for your help!

Hi All,I'm trying to exclude certain pages from the sitemap in Edge Delivery Services by updating the helix-query.yaml file. However, the changes are not being reflected when I access query-index.json.Even after publishing page, the last-modified date does update , but any structural changes—such as excluding paths or adding new properties—are not reflected in the output. Additionally, changes to the helix-sitemap.yaml file behave similarly and don’t seem to take effect.Here's a sample of the change I made in helix-query.yamlversion: 1indices: default: include: - '/**' exclude: - '/**.json' - '/configuration/**' - '/nav' - '/footer/**' - '/metadata/**' - '/index/vlp' - '/fragments/**' - '/style-guide/**' - '/spreadsheets/**' target: /query-index.json properties: lastModified: select: none value: parseTimestamp(headers["last-modified"], "ddd, DD MMM YYYY hh:mm:ss GMT") title: select: main h1:fi