Adobe Experience Manager API

Adobe Experience Manager (AEM) is a comprehensive content management solution for building websites, mobile apps, and forms, providing enterprise-grade digital experience management capabilities.

Power end-to-end data operations for your Adobe Experience Manager API API with Nexla. Our bi-directional Adobe Experience Manager API connector is purpose-built for Adobe Experience Manager API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Adobe Experience Manager API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Adobe Experience Manager API workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Adobe Experience Manager API credential in Nexla, you need to ensure that your AEM instance is accessible and that you have valid user credentials with appropriate permissions. The credential requires basic authentication with a username and password, and access to the PageInfo servlet endpoint.

1. AEM Instance Access: Ensure that your Adobe Experience Manager web application is accessible to Nexla. This typically requires network access to your AEM server, which may involve configuring firewall rules or VPN access depending on your infrastructure setup.

2. User Credentials: Obtain a username and password for an AEM user account that has permissions to access the PageInfo servlet and retrieve page information. The user account should have read permissions for the content you want to access through Nexla.

3. PageInfo Servlet URL: Identify the URL of your AEM instance's PageInfo servlet. This servlet is typically located at /libs/wcm/core/content/pageinfo.json relative to your AEM base URL. The complete URL usually follows the pattern https://[your-aem-instance]/libs/wcm/core/content/pageinfo.json.

   The PageInfo servlet provides JSON-formatted information about AEM pages and is used by Nexla to retrieve page data. For additional information about the PageInfo servlet and AEM authentication, see the Adobe Experience Manager documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Username	Yes	No	Your username
Password	Yes	Yes	Your password.
URL of your Adobe Experience Manager web application's PageInfo servlet	Yes	No	Link pointing to the PageInfo servlet of your app, exposed to the Web and accessible to Nexla. Usually ends with "pageinfo.json".

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Adobe Experience Manager API

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your AEM username in the Username field. This should be the username for an AEM user account that has permissions to access the PageInfo servlet and retrieve page information.

4. Enter your AEM password in the Password field. This password authenticates Nexla with your AEM instance using basic authentication. The password is securely stored and used in the Authorization header for all API requests.

5. Enter the complete URL of your AEM instance's PageInfo servlet in the URL of your Adobe Experience Manager web application's PageInfo servlet field. This URL should point to the PageInfo servlet endpoint, which is typically located at /libs/wcm/core/content/pageinfo.json relative to your AEM base URL. The URL should be accessible to Nexla and should include the protocol (https:// or http://) and the complete path to the servlet.

   The PageInfo servlet URL must be accessible from Nexla's network. If your AEM instance is behind a firewall or requires VPN access, ensure that Nexla has the necessary network access. The default URL format is https://example.net/libs/wcm/core/content/pageinfo.json, but you should replace this with your actual AEM instance URL.

   For additional information about AEM authentication and the PageInfo servlet, see the Adobe Experience Manager documentation.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Adobe Experience Manager API connector tile, then select the credential that will be used to connect to the Adobe Experience Manager API instance, and click Next; or, create a new Adobe Experience Manager API credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Adobe Experience Manager API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Index page

This endpoint retrieves page information for the index page of your AEM website. Use this endpoint when you need to access the main landing page or homepage content from your Adobe Experience Manager instance.

• This endpoint automatically retrieves page information for the index page located at /content/index in your AEM instance. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses the PageInfo servlet to retrieve JSON-formatted information about the page, including page properties, content structure, and metadata.
• The response includes detailed information about the page structure and content that can be used for content analysis, reporting, or integration with other systems.

The index page endpoint retrieves information about the main landing page of your AEM website. For detailed information about the PageInfo servlet and available page properties, see the Adobe Experience Manager documentation.

Retail Page

This endpoint retrieves page information for the retail page of your AEM website. Use this endpoint when you need to access retail or e-commerce related page content from your Adobe Experience Manager instance.

• This endpoint automatically retrieves page information for the retail page located at /content/we-retail in your AEM instance. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses the PageInfo servlet to retrieve JSON-formatted information about the page, including page properties, content structure, and metadata specific to retail content.
• The response includes detailed information about the retail page structure and content that can be used for e-commerce analysis, product catalog management, or integration with retail systems.

The retail page endpoint retrieves information about retail-specific content in your AEM website. For detailed information about the PageInfo servlet and available page properties, see the Adobe Experience Manager documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Adobe Experience Manager API data sources can also be manually configured to ingest data from any valid Adobe Experience Manager API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

For PageInfo servlet endpoints, the API URL typically follows the pattern {base_url}?path={page_path}, where {base_url} is your PageInfo servlet URL and {page_path} is the path to the AEM page you want to access. For additional information about AEM API endpoints and the PageInfo servlet, see the Adobe Experience Manager documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Adobe Experience Manager API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.