Chemaxon Database version management API

Endpoints to monitor and manage the different database versions and the automatic update process (the so-called "reindexing") from one version to another

GitHub OpenAPI

Operations 2

GET /rest-v1/db/versions/current/failed-structures Returns structures which could not be updated from the previous version #
GET /rest-v1/db/versions/current/status Returns status information about the database version #

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/chemaxon:chemaxon-database-version-management-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.

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

OpenAPI Specification

chemaxon-database-version-management-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Chemaxon Database version management API
  version: 26.1.3
  description: 'Operations tagged Database version management across 2 of this provider''s published API definitions: chemaxon-database-search-openapi.json, chemaxon-database-search-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://jchem-microservices.chemaxon.com/jwsdb
tags:
- description: Endpoints to monitor and manage the different database versions and the automatic update process (the so-called "reindexing") from one version to another
  name: Database version management
paths:
  /rest-v1/db/versions/current/failed-structures:
    get:
      description: 'Returns the IDs of all structures which could not be updated from the previous version and have not been explicitly deleted or replaced since the version update.


        Such structures are stored in the database and they can be used just like any other structure, except that all searches skip them.


        Failures during the automatic update process should be extremely rare, but if they do occur, you can use this endpoint to find them after the update is complete.'
      operationId: getFailedStructures
      responses:
        '200':
          content:
            '*/*':
              schema:
                $ref: '#/components/schemas/FailedStructuresResponse'
          description: Success.
      summary: Returns structures which could not be updated from the previous version
      tags:
      - Database version management
    servers:
    - url: https://jchem-microservices.chemaxon.com/jwsdb
  /rest-v1/db/versions/current/status:
    get:
      description: 'Returns information about the database version this service supports and its status in the connected database.


        The status can be:

        - UPDATING: the automatic updating (aka "reindexing") process is running. The response will also contain progress information.

        - READY: the service is ready to serve all requests.

        - READ_ONLY: the service can only serve non-modifying requests (e.g. search). This happens when database is being updated to a newer version, or this service was explicitly configured to be read-only.

        - DELETED: data has been removed. This happens when database has been updated to a newer version.'
      operationId: status
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DatabaseVersionStatusResponse'
          description: Success.
      summary: Returns status information about the database version
      tags:
      - Database version management
    servers:
    - url: https://jchem-microservices.chemaxon.com/jwsdb
components:
  schemas:
    FailedStructuresInTable:
      properties:
        ids:
          type: array
          items:
            type: integer
            format: int64
        tableName:
          type: string
    FailedStructuresResponse:
      properties:
        tables:
          type: array
          items:
            $ref: '#/components/schemas/FailedStructuresInTable'
        totalCount:
          type: integer
          format: int32
    DatabaseVersionStatusResponse:
      properties:
        progress:
          type: number
          format: double
        sinceJmsVersion:
          type: string
        status:
          type: string
          enum:
          - UPDATING
          - READY
          - READ_ONLY
          - DELETED
        totalCount:
          type: integer
          format: int64
        updatedCount:
          type: integer
          format: int64
        version:
          type: integer
          format: int32
x-refined-from:
- chemaxon-database-search-openapi.json
- chemaxon-database-search-openapi.yml