Postman

MockServer provides an official Postman collection for its REST control plane. It covers every control-plane endpoint — create expectations, verify requests, inspect recorded traffic, inject chaos, drive scenarios, set breakpoints, and manage server state — all from the Postman client. The collection is generated from MockServer's OpenAPI specification, so it always matches the running server.

Import the Collection

One click imports the collection — from the MockServer public workspace on the Postman API Network — straight into your Postman:

Or import it manually:

Download examples/postman/MockServer.postman_collection.json from the repository, then in Postman click Import and select the file.
The baseUrl collection variable defaults to http://localhost:1080. Change it to point at any MockServer instance.

Quick Start

Start MockServer with Docker:

docker run -d --rm -p 1080:1080 mockserver/mockserver

Each request carries a worked example body and documentation. A typical first run:

expectation → create expectation — registers a mock endpoint.
verify → verify a request has been received — asserts MockServer saw a request.
control → retrieve recorded requests — inspects what was received.
control → clears all expectations and recorded requests — resets state.

What the Collection Covers

The collection is organised into folders by area, covering all 68 control-plane endpoints:

Folder	What's in it
expectation	Create expectations (from JSON, an OpenAPI/Swagger spec, or a WSDL) and generate suggestions from unmatched requests
verify	Verify a request or a sequence was received; diff two requests field-by-field
control	Clear, reset, retrieve, status, bind ports, configuration, clock, proxy/mock mode, cassettes, replay, and request breakpoints
troubleshooting	Explain why requests did not match; per-expectation mismatch debugging
chaos	Register, list and live-patch service / TCP / gRPC chaos, plus scheduled multi-stage experiments
scenario	List, get, set and trigger stateful scenario state
drift	Retrieve and clear recorded mock drift
files / crud / import	File store, generated CRUD data stores, and HAR/Postman import
oidc / asyncapi / grpc / wasm / pact	Turnkey OIDC provider, AsyncAPI broker mocking, gRPC descriptors/health, WASM rule modules, and Pact contract export/verify

Prefer an open-source, git-native client? The same requests are available as a Bruno collection — both are generated from the same OpenAPI spec, so they stay identical.

The full control-plane API is documented as an OpenAPI spec on SwaggerHub.