Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Marketing / Adobe Experience Manager (AEM) API
Adobe Experience Manager (AEM) API logo

Adobe Experience Manager (AEM) API

0
AI ReadinessNon-Ready (F)0/100
See full scorecard
Community OpenAPI document · agent-readyMarketingContent Managementbasic48 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadobe.com%2Fadobe-aem" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadobe.com%2Fadobe-aem" | 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

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

GET

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

Get the AEM login page

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Adobe Experience Manager (AEM) API

- Non-Ready (F)
0/100
71
Foundational Compliance
56
Developer Experience & Jentic Compatibility
28
AI-Readiness & Agent Experience
94
Agent Usability
10
Security
0
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

29%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

28

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
13%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

10

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
10%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

0

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1
0%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Adobe Experience Manager API by hand means handling its basic auth and knowing Sling, OSGi, and JCR path conventions to hit the right console endpoints. Through Jentic you install once, import AEM from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

AEM exposes fixed console and JCR paths rather than a resource id you own in the URL, so you limit the agent to the operations it needs, such as running a QueryBuilder search or reading a content package. Because you pick the operations, configuration writes like the ReferrerFilter update stay out unless you include them.

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.

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

GET STARTED

Start building with Adobe Experience Manager (AEM) API

Explore with Jentic One
View OpenAPI Document