Apache Sling
Apache Sling is a RESTful web framework built on top of the Java Content Repository (JCR) standard. It maps HTTP requests to content resources using a resource-oriented URL decomposition model and uses scripts or servlets to render responses, supporting multiple scripting languages including HTL, JSP, Groovy, and server-side JavaScript. Apache Sling forms the foundation of Adobe Experience Manager (AEM) and is an Apache Software Foundation project with 300+ modular OSGi bundles.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Apache Sling the way a machine reads it — 28 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Apache Sling scores 31.8/100 (thin), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Apache Sling
Each block below is one kind of artifact we hold for Apache Sling. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache Sling Resource API
The Sling Resource API provides RESTful access to JCR content repository nodes via HTTP. Every content node is addressable as a URL, supporting GET, POST, PUT, DELETE, and MOVE ...
Apache Sling Scripting API
The Sling Scripting API enables server-side rendering through multiple scripting engines. Scripts are resolved from the content repository based on resource type and selectors, ...
Apache Sling Event API
The Sling Event API provides a job processing and eventing system built on OSGi EventAdmin. It supports distributed job queuing, scheduled job execution, event broadcasting acro...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apache Sling Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Apache Sling Finops
FINOPSFeatures 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Resource-Oriented REST API
Every JCR node is a REST resource accessible via URL with GET, POST, PUT, DELETE operations.
URL Decomposition
Flexible URL decomposition into resource path, selectors, extension, and suffix for content negotiation.
SlingPostServlet
Powerful POST servlet for content CRUD operations, supporting create, modify, delete, move, copy, and import.
Multi-Language Scripting
Server-side rendering with HTL, JSP, Groovy, FreeMarker, Thymeleaf, and Rhino JavaScript.
OSGi Modular Architecture
300+ modular OSGi bundles with hot-deploy capability and dynamic configuration.
Resource Type Hierarchy
Sling Resource Type system enables component inheritance and script resolution.
Event and Job Processing
Distributed job queue and event system for asynchronous content processing.
Health Check Framework
Extensible health check system for monitoring Sling instance components.
Replication and Distribution
Content distribution bundles for replicating content between Sling instances.
Scroll within the panel for all 9 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Content Management Systems
Build REST-based CMS solutions with JCR-backed content repositories.
Adobe Experience Manager
Foundation framework for AEM digital experience platform implementations.
Headless CMS
Serve structured JSON content via Sling's resource API for headless front-end applications.
Web Application Framework
Build OSGi-based Java web applications with RESTful resource routing.
Digital Asset Management
Manage and serve digital assets stored in JCR with metadata and rendition support.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Adobe Experience Manager
Apache Sling is the foundational framework for Adobe Experience Manager (AEM).
Apache Jackrabbit Oak
JCR implementation providing the content repository backend for Sling.
Apache Felix
OSGi framework container that hosts Sling bundles and manages the service registry.
Apache Karaf
OSGi runtime alternative for deploying Sling-based applications.
Maven
Maven plugin (slingstart-maven-plugin) and Maven archetypes for Sling development.
Elasticsearch
Search integration for indexing JCR content via Sling's indexing framework.
Resources
Every other property we hold for Apache Sling — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apache-sling · machine-readable index on apis.io