Adobe Experience Manager (AEM) API

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

★ Only Publicly Available OpenAPI DocumentMarketingContent Managementbasic48 EndpointsREST

For Agents

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Adobe Experience Manager (AEM) API

Explore with Jentic

View OpenAPI Document

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 your Jentic One instance 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 Jentic?

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

Credential isolation

Your AEM username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'install an aem package' or 'run an aem querybuilder query', and Jentic returns the matching AEM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

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.

Can I limit what my agent is allowed to do with the Adobe Experience Manager API?

Yes. Because Jentic One is self-hosted, you decide which AEM operations the agent may call, so you can allow only what a task needs, such as running a QueryBuilder search at /bin/querybuilder.json or downloading a content package, while leaving everything else off. Since AEM uses fixed console and JCR paths rather than a resource id you own, scoping happens at the operation level: a configuration write like the Sling ReferrerFilter update stays out unless you explicitly include it. The AEM basic auth credentials that grant this administrative access are held by your own Jentic One instance and injected only for the operations you permit.

Adobe Experience Manager (AEM) API

Connect the Adobe Experience Manager (AEM) API to your agent

Capabilities

Start building with Adobe Experience Manager (AEM) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs