Adobe Experience Manager (AEM) API

Name: Adobe Experience Manager (AEM) API API
Brand: Adobe Experience Manager (AEM) API
Availability: InStock

★ Only Publicly Available SpecMarketingContent Managementbasic48 EndpointsREST

For Agents

Administer Adobe Experience Manager environments by managing OSGi configurations, replication agents, packages, users, groups, and JCR content nodes through HTTP basic auth.

Quickstart

Get started with Adobe Experience Manager (AEM) API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"install an AEM content package"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adobe Experience Manager (AEM) API API.

Manage OSGi configurations across the Apache Felix HTTP service, Sling servlets, and AEM-specific bundles

Build, install, and download AEM content packages from /etc/packages for environment promotion

Configure replication agents to publish content from author to publish instances

Create and update users and groups under /home/users and /home/groups for access control

GET STARTED

Start building with Adobe Experience Manager (AEM) API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Adobe Experience Manager (AEM) API, keeping it validated and agent-ready.

Adobe Experience Manager (AEM) is Adobe's enterprise content management system used to author, manage, and publish digital experiences. This OpenAPI specification, maintained by Shine Solutions, exposes 48 endpoints for AEM administrative and content operations including OSGi configuration management, package management, replication agents, user and group administration, and JCR node operations. Use it to script AEM environment setup, configuration, and content lifecycle tasks. Authentication is HTTP basic against an AEM instance.

Use Cases

Patterns agents use Adobe Experience Manager (AEM) API API for, with concrete tasks.

★ AEM Environment Configuration as Code

Platform engineers automate AEM environment setup by applying OSGi configurations through POST /apps/system/config/{configNodeName} endpoints. Configurations for the Apache Felix HTTP service, Sling default GET servlet, referrer filter, and DavEx servlet can be set on every fresh environment without clicking through the AEM Web Console. This shortens environment build time from hours of manual config to a single scripted run.

Apply the production Apache Sling referrer filter configuration via POST /apps/system/config/org.apache.sling.security.impl.ReferrerFilter on the staging instance

Content Package Promotion

Release engineers move AEM content and code between environments by downloading packages from one instance and installing them on another using GET /etc/packages/{group}/{name}-{version}.zip and the package management endpoints. The API turns release promotion into an automatable pipeline rather than a manual upload through the package manager UI.

Download the latest version of the 'we-retail-content' package from the source instance and install it on the target via the AEM package endpoints

User and Group Administration

AEM admins manage users and groups under /home/users and /home/groups via the postAuthorizables endpoints, including creating new principals and assigning rights. This is useful for onboarding scripts that provision content authors with the correct group membership in one run.

Create a new AEM user 'jdoe' under /home/users via the postAuthorizables endpoint and add the user to the 'content-authors' group

Agent-Driven AEM Operations via Jentic

AI agents can execute routine AEM admin tasks through Jentic without learning the full Sling and OSGi configuration model up front. AEM basic auth credentials sit in the Jentic vault rather than in the agent's prompt, which matters because these credentials grant administrative access to the AEM instance.

Search Jentic for 'aem querybuilder', load GET /bin/querybuilder.json, and execute it with type=cq:Page and path=/content

Key Endpoints

48 endpoints — adobe experience manager (aem) is adobe's enterprise content management system used to author, manage, and publish digital experiences.

METHOD

PATH

DESCRIPTION

GET

/system/console/configMgr

Get the OSGi configuration manager state

POST

/apps/system/config/org.apache.sling.security.impl.ReferrerFilter

Configure the Sling referrer filter

GET

/etc/packages/{group}/{name}-{version}.zip

Download an AEM content package

GET

/bin/querybuilder.json

Run a JCR querybuilder query

POST

/.cqactions.html

Apply CQ ACL actions

GET

/libs/granite/core/content/login.html

Get the AEM login page

GET

/system/console/configMgr

Get the OSGi configuration manager state

POST

/apps/system/config/org.apache.sling.security.impl.ReferrerFilter

Configure the Sling referrer filter

GET

/etc/packages/{group}/{name}-{version}.zip

Download an AEM content package

GET

/bin/querybuilder.json

Run a JCR querybuilder query

POST

/.cqactions.html

Apply CQ ACL actions

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AEM basic auth credentials are stored encrypted in the Jentic vault. Because these credentials grant administrative access to the AEM instance, Jentic ensures the username and password never enter the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'install aem package' or 'aem querybuilder') and Jentic returns the matching operation with its input schema. The agent does not need prior knowledge of Sling or OSGi conventions to call the right endpoint.

Time to first call

Direct AEM integration: 1-3 days to handle basic auth, CSRF tokens for some endpoints, and Sling response shapes. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

HubSpot CMS Pages API

HubSpot's hosted CMS API for managing site pages and content.

Choose HubSpot CMS for SaaS-hosted content management with built-in CRM ties; choose AEM when you run an Adobe Experience Manager instance and need full OSGi/JCR control.

Complementary

Shopify Admin API

E-commerce storefront platform often paired with AEM for commerce-driven content.

Use Shopify for product, order, and storefront management; pair with AEM when AEM hosts the marketing content surrounding the storefront.

Complementary

Mailchimp API

Email marketing platform that distributes content authored in AEM.

Use Mailchimp to send email campaigns based on content authored in AEM; the two together cover authoring and distribution.

FAQs

Specific to using Adobe Experience Manager (AEM) API API through Jentic.

What authentication does the Adobe Experience Manager API use?

AEM uses HTTP basic authentication against the AEM instance. Credentials are sent in the Authorization header as base64 username:password. Through Jentic, these credentials are stored encrypted in the vault and never enter the agent's prompt context.

Can I install AEM content packages with the Adobe Experience Manager API?

Yes. The package endpoints under /etc/packages let you build, install, and download AEM content packages, which is the standard way to promote content and code between AEM environments. Combined with GET /etc/packages/{group}/{name}-{version}.zip, this enables full release pipelines.

How do I run a JCR query against AEM through Jentic?

Search Jentic for 'aem querybuilder', load GET /bin/querybuilder.json, and execute it with parameters like type=cq:Page and path=/content. Jentic returns the input schema so the agent supplies only the parameters AEM accepts.

What are the rate limits for the Adobe Experience Manager API?

AEM does not enforce rate limits at the API layer because it runs as your own instance. Throughput is bounded by your instance's hardware and JVM tuning rather than by Adobe-imposed quotas. Through Jentic, retries with backoff can be configured if a request times out.

Can I configure OSGi services with the Adobe Experience Manager API?

Yes. POST endpoints under /apps/system/config/{configNodeName} cover the Apache Felix HTTP service, Sling default GET servlet, referrer filter, DavEx servlet, password reset, and similar OSGi configurations. This is the basis for environment-as-code workflows.

Is the Adobe Experience Manager API free?

The API surface itself ships with AEM and has no separate API cost — access is included with your AEM licence. Operating costs are tied to the AEM environment you run it against. The Swagger spec for the API is maintained as an open-source project by Shine Solutions.