Adobe Experience Manager (AEM) API
★ Only Publicly Available OpenAPI DocumentMarketingContent 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.
Use for: I want to install an AEM content package on a publish instance, Configure the Apache Sling referrer filter on an AEM author instance, Create a new AEM user with a specific role, Run a querybuilder query for all pages under /content/we-retail
Not supported: Does not handle Adobe Analytics, Target, or Campaign — use for AEM author/publish instance administration, content packages, and JCR operations only.
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.
Install Jentic One Beta
Connect the Adobe Experience Manager (AEM) API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adobe Experience Manager (AEM) API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Adobe Experience Manager (AEM) 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
Run JCR querybuilder queries via /bin/querybuilder.json to find content nodes by criteria
Trigger health checks against AEM bundles to confirm environment readiness
Use Cases
Patterns agents use Adobe Experience Manager (AEM) 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
GET
/libs/granite/core/content/login.html
Get the AEM login page
Why 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.
FAQs
Specific to using Adobe Experience Manager (AEM) 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.
GET STARTED