dotCMS

dotCMS Elasticsearch Content Search API

Backend Elasticsearch search endpoints for portlet context

Documentation GitHub OpenAPI

Operations 3

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /api/es/layout/{params} Get the search portlet layout · Get layout 4 #

Ask an LLM

“What does the Elasticsearch portlet layout endpoint return?”

“Can I load the search tool's layout with path parameters?”

Tell an agent

Get the Elasticsearch portlet layout for {params}.

Load the ES search tool layout using {params}.

POST /api/es/search Search content with a JSON query · Search content using a search query (POST) #

Ask an LLM

“How do I search dotCMS content with an Elasticsearch-style JSON query?”

“Can I include related content in search results, and how deep?”

Tell an agent

Search content with my JSON query, returning related content to depth {depth}.

Run this JSON content search against live content only: {live}.

POST /api/es/raw Run a raw search query · Execute raw search query (POST) #

Ask an LLM

“Can I get the unprocessed search engine response for a JSON query?”

“Is there a search that returns hits and aggregations without contentlet processing?”

Tell an agent

Run this raw JSON query and return the search engine's unprocessed response.

Execute my aggregation query as a raw search.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/dotcms:dotcms-elasticsearch-content-search-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: dotCMS REST Elasticsearch Content Search API
  version: '3'
  description: Backend Elasticsearch search endpoints for portlet context
servers:
- url: /
  description: dotCMS Server
tags:
- name: Elasticsearch Content Search
  description: Backend Elasticsearch search endpoints for portlet context
paths:
  /api/es/layout/{params}:
    get:
      tags:
      - Elasticsearch Content Search
      operationId: getLayout_4
      parameters:
      - name: params
        in: path
        required: true
        schema:
          pattern: .*
          type: string
      responses:
        default:
          description: default response
          content:
            text/html: {}
      summary: Get layout 4
      x-summary-source: derived
  /api/es/search:
    post:
      tags:
      - Elasticsearch Content Search
      summary: Search content using a search query (POST)
      description: Executes a JSON search query against dotCMS content in a portlet context. The request body accepts an Elasticsearch/OpenSearch JSON query. The query is routed through the phase-aware search API, so it targets whichever engine the active OpenSearch migration phase selects (Elasticsearch in phases 0-1, OpenSearch in phases 2-3). Results include the matching contentlets plus the search response metadata under 'esresponse', which retains the legacy Elasticsearch-wire shape (took, hits.total, hits.hits[]._id/._index/._score/._source, aggregations) for backward compatibility, regardless of the engine that served the query.
      operationId: searchContentByESPost
      parameters:
      - name: depth
        in: query
        description: 'Depth of related content to include: 0=identifiers only, 1=related contentlets, 2=related contentlets with their related identifiers, 3=related contentlets with their related contentlets. Omit to exclude relationships.'
        schema:
          type: string
      - name: live
        in: query
        description: If true, search only live content; if false, search working content
        schema:
          type: boolean
      - name: userid
        in: query
        description: 'Admin-only: run the query under the permission context of this user ID or email address'
        schema:
          type: string
      - name: allCategoriesInfo
        in: query
        description: If true, return full category details (key, name, description); if false, return only category names
        schema:
          type: boolean
      requestBody:
        content:
          application/json:
            schema:
              type: string
      responses:
        '200':
          description: Search results returned successfully
          content:
            application/json:
              schema:
                type: object
                description: Search results containing the matching contentlets and the Elasticsearch-wire response metadata under 'esresponse'
        '400':
          description: Invalid Elasticsearch query syntax
          content:
            application/json: {}
        '401':
          description: Authentication required
          content:
            application/json: {}
  /api/es/raw:
    post:
      tags:
      - Elasticsearch Content Search
      summary: Execute raw search query (POST)
      description: Executes a raw JSON search query and returns the unprocessed search response in a portlet context. The request body accepts an Elasticsearch/OpenSearch JSON query. Unlike the /search endpoint, results are returned directly from the search engine without additional contentlet processing. The query is routed through the phase-aware search API, so it targets whichever engine the active OpenSearch migration phase selects (Elasticsearch in phases 0-1, OpenSearch in phases 2-3). The response preserves the legacy Elasticsearch-wire shape (took, hits.total, hits.hits[]._id/._index/._score/._source, aggregations, suggest) for backward compatibility, regardless of the engine that served the query.
      operationId: rawSearchContentByESPost
      responses:
        '200':
          description: Search response returned successfully
          content:
            application/json:
              schema:
                type: object
                description: Search response in the legacy Elasticsearch-wire shape (took, hits, aggregations, suggest)
        '400':
          description: Invalid Elasticsearch query
          content:
            application/json: {}
        '401':
          description: Authentication required
          content:
            application/json: {}
x-provenance:
  method: harvested
  publisher: dotCMS
  source: https://demo.dotcms.com/api/openapi.json
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)

dotCMS Elasticsearch Content Search API

Operations 3

Documentation

Specifications

Other Resources

Work with this as data

MCP server

Tools for apis

Call it yourself

Get an API key

OpenAPI Specification