Netcracker Composite Controller API

The Composite Controller API from Netcracker — 3 operation(s) for composite controller.

Operations 4

POST /api/composite/v1/structures Save or update composite
GET /api/composite/v1/structures Get all composite structures
GET /api/composite/v1/structures/{compositeId} Get composite structure by composite id
DELETE /api/composite/v1/structures/{compositeId}/delete Delete composite by composite id

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/netcracker-composite-controller-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

netcracker-composite-controller-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: DBaaS Aggregator Composite Controller API
  version: 6.13.2
  description: This documentation presents the REST API for the "Database as a Service" (DBaaS) component. DBaaS acts as an aggregator for all adapters. It is designed to collect requests for managed databases and route them to the appropriate adapter. DBaaS stores information about all databases used in a cloud project. These databases are isolated by namespace. DBaaS uses a Classifier to identify databases within a cloud namespace. The Classifier includes service-related information such as scope, microservice name, tenant ID, and namespace.
tags:
- name: Composite Controller
paths:
  /api/composite/v1/structures:
    post:
      summary: Save or update composite
      description: Create a new composite structure or update an existing one.
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CompositeStructureDto'
        required: true
      responses:
        '204':
          description: Composite is saved
        '400':
          description: Validation error
        '409':
          description: Conflict error. Namespace in request body is already associated with another composite structure
        '500':
          description: Internal server error
        '401':
          description: Not Authorized
        '403':
          description: Not Allowed
      tags:
      - Composite Controller
      security:
      - SecurityScheme:
        - DB_CLIENT
    get:
      summary: Get all composite structures
      description: Retrieve all composite structures that are registered in DBaaS.
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema: {}
        '500':
          description: Internal server error
        '401':
          description: Not Authorized
        '403':
          description: Not Allowed
      tags:
      - Composite Controller
      security:
      - SecurityScheme:
        - DB_CLIENT
  /api/composite/v1/structures/{compositeId}:
    get:
      summary: Get composite structure by composite id
      description: Retrieve a composite structure by its Id. Composite id by design is baseline or baseline origin if namespace in blue-green
      parameters:
      - name: compositeId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Composite is found
          content:
            application/json:
              schema: {}
        '404':
          description: Composite not found
        '500':
          description: Internal server error
        '401':
          description: Not Authorized
        '403':
          description: Not Allowed
      tags:
      - Composite Controller
      security:
      - SecurityScheme:
        - DB_CLIENT
  /api/composite/v1/structures/{compositeId}/delete:
    delete:
      summary: Delete composite by composite id
      description: Delete a composite structure by its ID.
      parameters:
      - name: compositeId
        in: path
        required: true
        schema:
          type: string
      responses:
        '204':
          description: Composite is deleted successfully
        '404':
          description: Composite not found
        '500':
          description: Internal server error
        '401':
          description: Not Authorized
        '403':
          description: Not Allowed
      tags:
      - Composite Controller
      security:
      - SecurityScheme:
        - DB_CLIENT
components:
  schemas:
    CompositeStructureDto:
      type: object
      required:
      - id
      - namespaces
      properties:
        id:
          type: string
          description: Composite identifier. Usually it's baseline or origin baseline in blue-green scheme
        namespaces:
          type: array
          uniqueItems: true
          items:
            type: string
          description: Namespaces that are included in composite structure (baseline and satellites)
  securitySchemes:
    SecurityScheme:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Authentication