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 mock API

Operations related to API and Services mocks

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

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

This API exposes 10 operations across 9 paths, and defines 24 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.

10 operations 9 paths 24 schemas 1 DELETE6 GET1 POST2 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 mock 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 10

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

mock 10

Operations related to API and Services mocks

GET
/services
Get Services and APIs
GetServices 2 params → 200
GET
/services/count
Get the Services counter
GetServicesCounter → 200
GET
/services/{id}
Get Service
GetService 2 params → 200
DELETE
/services/{id}
Delete Service
DeleteService 1 param → 200
PUT
/services/{id}/operation
Override Service Operation
OverrideServiceOperation 2 params body → 200500
PUT
/services/{id}/metadata
Update Service Metadata
UpdateServiceMetadata 1 param body → 200500
GET
/services/search
Search for Services and APIs
SearchServices 1 param → 200
POST
/import
Import a snapshot
importSnapshot body → 201
GET
/export
Export a snapshot
exportSnapshot 1 param → 200
GET
/services/labels
Get the already used labels for Services
GetServicesLabels → 200

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Operation (13 properties), Service (8 properties), Binding (7 properties), Message (6 properties). Each schema is shown below with its type and property counts.

Metadata
object
Commodity object for holding metadata on any entity. This object is inspired by Kubernetes metadata.
4 properties 2 required
StringArray
array
A simple array of String
Header
object
Transport headers for both Requests and Responses
2 properties 2 required
UnidirectionalEvent
object
Representation of an unidirectional exchange as an event message
Binding
object
Protocol binding details for asynchronous operations
7 properties 2 required
Service
object
Represents a Service or API definition as registred into Microcks repository
8 properties 4 required
Message
object
Common structure for Request, Response and EventMessage
6 properties 2 required
AbstractExchange
object
Abstract bean representing a Service or API Exchange.
1 property 1 required
ServiceView
object
Aggregate bean for grouping a Service an its messages pairs
2 properties 2 required
LabelsMap
object
A map which keys are already used labels keys and values are already used values for this key
MessageArray
array
Array of Exchanges for Service operations
TriggerInfo
object
Information on a sync-to-async trigger.
3 properties 3 required
CallbackInfo
object
Information on a REST api/service callback
3 properties 2 required
Parameter
object
Companion objects for Request representing query parameter
2 properties 2 required
Request
A mock invocation or test request
Operation
object
An Operation of a Service or API
13 properties 2 required
Exchange
Abstract representation of a Service or API exchange type (request/response, event based, ...)
ParameterConstraint
object
Companion object for Operation that may be used to express constraints on request parameters
5 properties 1 required
Counter
object
A simple Counter type.
1 property
SnapshotUpload
object
Upload of a repository snapshot file
1 property 1 required
EventMessage
object
A simple event message published or received in an asynchronous exchange
RequestResponsePair
object
Request associated with corresponding Response
Response
A mock invocation or test response
OperationOverrideDTO
object
Data Transfer object for grouping the mutable properties of an Operation
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microcks-mock-api-openapi.yml Raw ↑

Other APIs Microcks publishes across the network.

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

This is an independent, third-party profile of Microcks mock 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.