canonical: https://jentic.com/apis/wiremock.org/wiremock

# WireMock

WireMock offers a REST API for administration, troubleshooting and analysis purposes. The API exposes 39 endpoints.

## For AI agents

Programmatically create a new stub mapping, get all stub mappings. Covers 39 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a new stub mapping
- Get all stub mappings
- Delete all stub mappings
- Reset stub mappings
- Persist stub mappings
- Import stub mappings

## Use cases

### Developer Tools Operations

Use the WireMock to perform developer tools operations programmatically. The API provides 39 endpoints covering core functionality including create a new stub mapping, get all stub mappings, delete all stub mappings.

Example prompt: Call POST `/__admin/mappings` to create a new stub mapping

### Automated Stub Mappings Management

Automate stub mappings operations by combining multiple WireMock endpoints. Agents can get all stub mappings and then delete all stub mappings in a single workflow.

Example prompt: Call GET `/__admin/mappings` to get all stub mappings, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call WireMock endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'create a new stub mapping', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/__admin/mappings` | Create a new stub mapping |
| GET | `/__admin/mappings` | Get all stub mappings |
| DELETE | `/__admin/mappings` | Delete all stub mappings |
| POST | `/__admin/mappings/reset` | Reset stub mappings |
| POST | `/__admin/mappings/save` | Persist stub mappings |
| POST | `/__admin/mappings/import` | Import stub mappings |
| GET | `/__admin/mappings/{stubMappingId}` | Get stub mapping by ID |
| PUT | `/__admin/mappings/{stubMappingId}` | Update a stub mapping |

## Key resources

- **Stub Mappings** — Operations on stub mappings
- **Requests** — Logged requests and responses received by the mock service
- **Near Misses** — Near misses allow querying of received requests or request patterns according to similarity
- **Recordings** — Stub mapping record and snapshot functions
- **Scenarios** — Scenarios support modelling of stateful behaviour

## Why Jentic

- **Setup:** Wiring the WireMock admin API by hand means pointing at your running WireMock instance, composing its __admin stub and mapping calls, and parsing the responses yourself. Through Jentic you install once, import WireMock from the API Directory, store the connection once, and your agent calls it.
- **Permission scoping:** WireMock puts the stub mapping id in the URL path (`/__admin/mappings/{stubMappingId}`), so a rule can pin your agent to reading or updating one mapping. You choose the operations it may call, so destructive ones like resetting or deleting all mappings are not included unless you add them.
- **Credential handling:** Any WireMock connection detail is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a stub mapping' or 'list current mappings', and Jentic returns the matching WireMock operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the WireMock use?

The WireMock uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a new stub mapping with the WireMock?

Yes. Use the POST `/__admin/mappings` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the WireMock?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a new stub mapping through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new stub mapping'. Jentic returns the matching WireMock operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the WireMock have?

The WireMock exposes 39 endpoints covering stub mappings, requests, near misses operations.

### Can I limit what my agent is allowed to do with the WireMock API?

Yes. Jentic One is self-hosted, so your own rules decide which WireMock operations and connection details the agent may use. Because WireMock puts the stub mapping ID in the URL path (`/__admin/mappings/{stubMappingId}`), you can pin the agent to reading or updating a single mapping rather than the whole set. You choose the exact operations it can call, so destructive actions like resetting or deleting all mappings stay out of reach unless you explicitly grant them.