Lucidworks Solr admin API

The Solr Admin API lets you send commands to Solr through Fusion's proxy service. This allows you to protect your Solr instances from outside connections, and apply roles and user permissions from Fusion when running Solr commands. Requests sent to this API are subject to access restrictions above the collection level. Note that because one `searchCluster` may host several collections, it is not recommended to use this with a collection-level command (such as a query, or document update).

Operations 7

GET /solrAdmin/{solrApiPath}/{path} Send a Solr command #
PUT /solrAdmin/{solrApiPath}/{path} Send a Solr command #
POST /solrAdmin/{solrApiPath}/{path} Send a Solr command #
DELETE /solrAdmin/{solrApiPath}/{path} Send a Solr command #
OPTIONS /solrAdmin/{solrApiPath}/{path} List Solr command options #
HEAD /solrAdmin/{solrApiPath}/{path} Send an HTTP HEAD request #
GET /solrAdmin/status Get Solr admin service status #

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/lucidworks:lucidworks-solr-admin-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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

OpenAPI Specification

lucidworks-solr-admin-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Fusion Admin Solr admin API
  description: These APIs provide general administrative functions for your Fusion instance. Use these APIs to manage Fusion objects, App Studio objects, connections to Solr clusters, license files, job schedules, and more. You can also use them to create a history of service events.
  termsOfService: https://lucidworks.com/legal/developer-license-agreement/
  contact:
    name: Lucidworks
    url: www.lucidworks.com
    email: support@lucidworks.com
  license:
    name: License of API
    url: https://lucidworks.com/legal/developer-license-agreement/
  version: '5.9'
servers:
- url: https://{FUSION HOST}/api
  description: Fusion
  variables:
    FUSION HOST:
      default: FUSION_HOST
      description: Your environment host.
- url: https://{FUSION HOST}/api/apps/{APP_NAME}
  description: Fusion app
  variables:
    FUSION HOST:
      default: FUSION_HOST
      description: Your environment host.
    APP_NAME:
      default: APP_NAME
      description: The name of your Fusion application.
tags:
- name: Solr admin
  description: 'The Solr Admin API lets you send commands to Solr through Fusion''s proxy service. This allows you to protect your Solr instances from outside connections, and apply roles and user permissions from Fusion when running Solr commands. Requests sent to this API are subject to access restrictions above the collection level.


    Note that because one `searchCluster` may host several collections, it is not recommended to use this with a collection-level command (such as a query, or document update).'
paths:
  /solrAdmin/{solrApiPath}/{path}:
    get:
      tags:
      - Solr admin
      summary: Send a Solr command
      description: 'Issue a Solr command to the search cluster.


        Note that because one searchCluster may host several collections, it is not recommended to use this with a collection-level command (such as a query, or document update).'
      operationId: proxyGetRequestToSolr
      parameters:
      - name: solrApiPath
        in: path
        description: The Solr API Path.
        required: true
        schema:
          type: string
      - name: path
        in: path
        description: The path to the Solr command to run.
        required: true
        schema:
          pattern: .*
          type: string
      responses:
        '200':
          description: successful operation
          content:
            application/json:
              schema:
                type: object
                description: Solr metadata output
                additionalProperties: true
              examples:
                solrMBeans:
                  summary: This is the response to GET all CORE MBeans for the default search cluster.
                  value:
                    responseHeader:
                      status: 0
                      QTime: 1
                    solr-mbeans:
                    - CORE
                    - searcher:
                        class: org.apache.solr.search.SolrIndexSearcher
                        version: '1.0'
                        description: index searcher
                        src: null
                      core:
                        class: collection1
                        version: '1.0'
                        description: SolrCore
                        src: null
                      Searcher@435cf502[collection1] main:
                        class: org.apache.solr.search.SolrIndexSearcher
                        version: '1.0'
                        description: index searcher
                        src: null
    put:
      tags:
      - Solr admin
      summary: Send a Solr command
      description: 'Issue a Solr command to the search cluster.


        Note that because one searchCluster may host several collections, it is not recommended to use this with a collection-level command (such as a query, or document update).'
      operationId: proxyPutRequestToSolr
      parameters:
      - name: solrApiPath
        in: path
        description: The Solr API Path.
        required: true
        schema:
          type: string
      - name: path
        in: path
        description: The path to the Solr command to run.
        required: true
        schema:
          pattern: .*
          type: string
      requestBody:
        description: Solr request object.
        content:
          '*/*':
            schema:
              $ref: '#/components/schemas/InputStream'
        required: false
      responses:
        '200':
          description: successful operation
          content: {}
      x-codegen-request-body-name: body
    post:
      tags:
      - Solr admin
      summary: Send a Solr command
      description: 'Issue a Solr command to the search cluster.


        Note that because one searchCluster may host several collections, it is not recommended to use this with a collection-level command (such as a query, or document update).'
      operationId: proxyPostRequestToSolr
      parameters:
      - name: solrApiPath
        in: path
        description: The Solr API Path.
        required: true
        schema:
          type: string
      - name: path
        in: path
        description: The path to the Solr command to run.
        required: true
        schema:
          pattern: .*
          type: string
      requestBody:
        description: Solr request body.
        content:
          '*/*':
            schema:
              $ref: '#/components/schemas/InputStream'
        required: false
      responses:
        '200':
          description: successful operation
          content: {}
      x-codegen-request-body-name: body
    delete:
      tags:
      - Solr admin
      summary: Send a Solr command
      description: 'Issue a Solr command to the search cluster.


        Note that because one searchCluster may host several collections, it is not recommended to use this with a collection-level command (such as a query, or document update).'
      operationId: proxyDeleteRequestToSolr
      parameters:
      - name: solrApiPath
        in: path
        description: The Solr API Path.
        required: true
        schema:
          type: string
      - name: path
        in: path
        description: The path to the Solr command to run.
        required: true
        schema:
          pattern: .*
          type: string
      responses:
        '200':
          description: successful operation
          content: {}
    options:
      tags:
      - Solr admin
      summary: List Solr command options
      description: Get the options for a Solr command.
      operationId: proxyOptionsRequestToSolr
      parameters:
      - name: solrApiPath
        in: path
        description: The Solr API Path.
        required: true
        schema:
          type: string
      - name: path
        in: path
        description: The path to the Solr command to run.
        required: true
        schema:
          pattern: .*
          type: string
      responses:
        '200':
          description: successful operation
          content: {}
    head:
      tags:
      - Solr admin
      summary: Send an HTTP HEAD request
      description: Issue an HTTP HEAD request to the Solr cluster.
      operationId: proxyHeadRequestToSolr
      parameters:
      - name: solrApiPath
        in: path
        description: The Solr API Path.
        required: true
        schema:
          type: string
      - name: path
        in: path
        description: The path for the HTTP request.
        required: true
        schema:
          pattern: .*
          type: string
      responses:
        '200':
          description: successful operation
          content: {}
  /solrAdmin/status:
    get:
      tags:
      - Solr admin
      summary: Get Solr admin service status
      description: Check the status of the Solr Admin service.
      operationId: getStatus_22
      responses:
        '200':
          description: successful operation
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ServiceStatus'
components:
  schemas:
    InputStream:
      type: object
    ServiceStatus:
      type: object
      properties:
        status:
          type: string
          enum:
          - starting
          - ok
          - warning
          - error
          - shutdown
        node:
          type: string
          readOnly: true
        messages:
          type: array
          readOnly: true
          items:
            $ref: '#/components/schemas/StatusMessage'
    StatusMessage:
      type: object
      properties:
        date:
          type: string
          format: date-time
          readOnly: true
        message:
          type: string
          readOnly: true
  securitySchemes:
    Basic_auth:
      type: http
      scheme: basic
    API_key:
      name: x-api-key
      type: apiKey
      in: header
x-original-swagger-version: '2.0'
x-provenance:
  method: harvested
  publisher: Lucidworks
  source: https://doc.lucidworks.com/api-reference/5.9/fusion-api-swagger.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)