# MockServer ## Docs - [Expectations API](https://moeck.io/api/expectations.md): Create, update, and load expectations using PUT /mockserver/expectation and PUT /mockserver/openapi. - [API Overview](https://moeck.io/api/overview.md): MockServer exposes a REST API over HTTP or HTTPS. All endpoints use the PUT method with JSON request bodies. - [State API](https://moeck.io/api/state.md): Retrieve recorded requests and logs, clear state selectively, reset everything, check server status, and bind additional ports. - [Verification API](https://moeck.io/api/verification.md): Verify that MockServer received specific requests using PUT /mockserver/verify and PUT /mockserver/verifySequence. - [Java Client](https://moeck.io/clients/java.md): Control MockServer from Java using MockServerClient or ClientAndServer. - [JavaScript Client](https://moeck.io/clients/javascript.md): Control MockServer from Node.js or the browser using the mockserver-client package. - [Ruby Client](https://moeck.io/clients/ruby.md): Control MockServer from Ruby using the community-maintained mockserver-client gem. - [Properties](https://moeck.io/configuration/properties.md): Configure MockServer using property files, system properties, environment variables, or Java code. - [Security](https://moeck.io/configuration/security.md): Restrict who can create and modify expectations using JWT bearer token or mutual TLS authentication on the MockServer control plane. - [TLS / HTTPS](https://moeck.io/configuration/tls.md): Configure TLS for inbound HTTPS connections, mutual TLS client authentication, and outbound TLS when forwarding to HTTPS backends. - [Logs & State](https://moeck.io/debugging/logs-and-state.md): Retrieve recorded requests, active expectations, and logs via the REST API. Clear or reset state between tests. Persist expectations to survive restarts. - [MockServer UI](https://moeck.io/debugging/ui.md): Use the built-in dashboard to inspect logs, active expectations, received requests, and proxied requests in real time. - [Introduction](https://moeck.io/introduction.md): MockServer lets you mock and proxy any HTTP or HTTPS service for testing, local development, and CI pipelines. - [Expectations](https://moeck.io/mocking/expectations.md): Define what MockServer should do when it receives a matching request. - [OpenAPI](https://moeck.io/mocking/openapi.md): Load an OpenAPI v3 spec to auto-generate expectations or use it as a request matcher. - [Request Matchers](https://moeck.io/mocking/request-matchers.md): Match incoming requests by method, path, headers, body, and more. - [Response Actions](https://moeck.io/mocking/response-actions.md): Define what MockServer returns when an expectation matches: a response, a forward, a callback, or an error. - [Response Templates](https://moeck.io/mocking/response-templates.md): Generate dynamic responses using Mustache, Velocity, or JavaScript templates. - [Verification](https://moeck.io/mocking/verification.md): Assert that MockServer received the requests you expected. - [Proxy Overview](https://moeck.io/proxying/overview.md): Use MockServer as a proxy to intercept, record, and inspect HTTP and HTTPS traffic between your application and real services. - [Record & Replay](https://moeck.io/proxying/record-replay.md): Proxy live traffic to record real requests and responses, then replay them as mock expectations so your tests no longer depend on the real service. - [Quick Start](https://moeck.io/quickstart.md): Get MockServer running and mock your first HTTP request in under 5 minutes. - [Running MockServer](https://moeck.io/running-mockserver.md): Deploy MockServer via Docker, Helm, Maven, npm, standalone JAR, JUnit 4/5, or Spring.