Sonatype Nexus Repository

Sonatype Nexus Repository Security management: secrets encryption API

The Security management: secrets encryption API from Sonatype Nexus Repository — 1 operation(s) for security management: secrets encryption.

Documentation GitHub OpenAPI

Operations 1

PUT /v1/secrets/encryption/re-encrypt Re-encrypt secrets using the specified key #

Specifications

⚙

OpenAPI

https://artifacts.apis.io/nexus/openapi/nexus-security-management-secrets-encryption-api-openapi.yml

Schemas & Data

📊

JSONSchema

https://artifacts.apis.io/nexus/json-schema/nexus-re-encryption-request-api-xo-schema.json

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/nexus:nexus-security-management-secrets-encryption-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: 'Nexus Repository Manager REST Security management: secrets…'
  version: 3.97.2-02
servers:
- url: /service/rest
tags:
- name: 'Security management: secrets encryption'
paths:
  /v1/secrets/encryption/re-encrypt:
    put:
      tags:
      - 'Security management: secrets encryption'
      summary: Re-encrypt secrets using the specified key
      description: Ensure all nodes have access to the key, and they use the same key
      operationId: updateSecretsEncryptionReEncrypt
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReEncryptionRequestApiXO'
      responses:
        '202':
          description: Re-encrypt task successfully submitted
        '400':
          description: 'Invalid request. See the response for more information. Possible causes: The key is not available to all nodes, upgrade needed or empty key id.'
        '403':
          description: Insufficient permissions to re-encrypt secrets
        '409':
          description: Re-encryption task in progress.
components:
  schemas:
    ReEncryptionRequestApiXO:
      required:
      - secretKeyId
      type: object
      properties:
        secretKeyId:
          minLength: 1
          type: string
          description: Key identifier that will be used to re-encrypt secrets
        notifyEmail:
          type: string
          description: Optional - Email to notify when task finishes