Sonatype Nexus Repository Routing rules API

The Routing rules API from Sonatype Nexus Repository — 2 operation(s) for routing rules.

Operations 5

GET /v1/routing-rules List routing rules #
POST /v1/routing-rules Create a single routing rule #
GET /v1/routing-rules/{name} Get a single routing rule #
PUT /v1/routing-rules/{name} Update a single routing rule #
DELETE /v1/routing-rules/{name} Delete a single routing rule #

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-routing-rules-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

nexus-routing-rules-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Nexus Repository Manager REST Routing rules API
  version: 3.97.2-02
servers:
- url: /service/rest
tags:
- name: Routing Rules
paths:
  /v1/routing-rules:
    get:
      tags:
      - Routing Rules
      summary: List routing rules
      operationId: listRoutingRules
      responses:
        '200':
          description: Routing rules returned
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/RoutingRuleXO'
        '403':
          description: Insufficient permissions to read routing rules
    post:
      tags:
      - Routing Rules
      summary: Create a single routing rule
      operationId: createRoutingRules
      requestBody:
        description: A routing rule configuration
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RoutingRuleXO'
        required: true
      responses:
        '204':
          description: Routing rule was successfully created
        '400':
          description: A routing rule with the same name already exists or required parameters missing
        '403':
          description: Insufficient permissions to create routing rule
  /v1/routing-rules/{name}:
    get:
      tags:
      - Routing Rules
      summary: Get a single routing rule
      operationId: getRoutingRules
      parameters:
      - name: name
        in: path
        description: The name of the routing rule to get
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Routing rule returned
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RoutingRuleXO'
        '403':
          description: Insufficient permissions to read routing rules
        '404':
          description: Routing rule not found
    put:
      tags:
      - Routing Rules
      summary: Update a single routing rule
      operationId: updateRoutingRules
      parameters:
      - name: name
        in: path
        description: The name of the routing rule to update
        required: true
        schema:
          type: string
      requestBody:
        description: A routing rule configuration
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RoutingRuleXO'
        required: true
      responses:
        '204':
          description: Routing rule was successfully updated
        '400':
          description: Another routing rule with the same name already exists or required parameters missing
        '403':
          description: Insufficient permissions to edit routing rules
        '404':
          description: Routing rule not found
    delete:
      tags:
      - Routing Rules
      summary: Delete a single routing rule
      operationId: deleteRoutingRules
      parameters:
      - name: name
        in: path
        description: The name of the routing rule to delete
        required: true
        schema:
          type: string
      responses:
        '204':
          description: Routing rule was successfully deleted
        '403':
          description: Insufficient permissions to delete routing rules
        '404':
          description: Routing rule not found
components:
  schemas:
    RoutingRuleXO:
      type: object
      properties:
        name:
          pattern: ^[a-zA-Z0-9\-]{1}[a-zA-Z0-9_\-\.]*$
          type: string
        description:
          type: string
        mode:
          type: string
          description: Determines what should be done with requests when their path matches any of the matchers
          enum:
          - ALLOW
          - BLOCK
        matchers:
          type: array
          description: Regular expressions used to identify request paths that are allowed or blocked (depending on mode)
          items:
            type: string
            description: Regular expressions used to identify request paths that are allowed or blocked (depending on mode)