How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microcks config API

Operations related to configuration

Microcks config API is one of 6 APIs that Microcks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Config. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 9 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.14.0.

Requests are made against a single base URL, http://microcks.example.com/api.

9 operations 6 paths 3 schemas 1 DELETE6 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.14.0
Server
http://microcks.example.com/api
Authentication
OAuth 2.0
License
Resource Areas
1

Authentication & Security 1

Microcks config API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (jwt-bearer) using the clientCredentials flow, exposing 3 scopes. By default, every request must be authenticated.

  • jwt-bearer — JWT Bearer acquired using OAuth 2 Authentication flow or Direct Access Grant

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 1 DELETE, 6 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

config 9

Operations related to configuration

GET
/secrets
Get Secrets
GetSecrets 2 params → 200
POST
/secrets
Create a new Secret
CreateSecret body → 201
GET
/secrets/{id}
Get Secret
GetSecret 1 param → 200
PUT
/secrets/{id}
Update Secret
UpdateSecret 1 param body → 200
DELETE
/secrets/{id}
Delete Secret
DeleteSecret 1 param → 200
GET
/secrets/count
Get the Secrets counter
GetSecretsCounter → 200
GET
/keycloak/config
Get authentification configuration
GetKeycloakConfig → 200
GET
/features/config
Get features configuration
GetFeaturesConfig → 200
GET
/secrets/search
Search for Secrets
SearchSecrets 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Secret (8 properties), KeycloakConfig (6 properties), Counter (1 property). Each schema is shown below with its type and property counts.

Secret
object
A Secret allows grouping informations on how to access a restricted resource such as a repsoitory URL. Secrets are typically used by ImpoortJobs.
8 properties 2 required
KeycloakConfig
object
Representation of Keycloak / SSO configuration used by Microcks server
6 properties 6 required
Counter
object
A simple Counter type.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microcks-config-api-openapi.yml Raw ↑

Other APIs Microcks publishes across the network.

Microcks job API
Microcks metrics API
Microcks mock API
Microcks Resources API
Microcks test API
Where this information came from

This is an independent, third-party profile of Microcks config API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.