A WireMock simulation of Chase JPMorgan's REST API — covering check issuance, search, image retrieval, print requests with status reads, stop payments, revocation, and cancellation.
A shared instance of this template runs on a public endpoint — call it right now from curl, an SDK, or an AI agent. Responses are fixed examples and behavior can't be changed; rate limits apply.
Jump to the endpoints ↓Run this template as a mock API in WireMock Cloud for a private instance you control — edit stubs, add stateful scenarios, use dynamic response templating, and inspect requests in the log.
Open in WireMock Cloud (free) →Live sandbox · no signup, no API key
A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.
Endpoints
POST Search Checks - 200
curl -s -X POST 'https://dge4e.wiremockapi.cloud/checks/search' \
-H 'Content-Type: application/json' \
-d '{}'GET Get Check Health - 200
curl -s -X GET 'https://dge4e.wiremockapi.cloud/checks/health'POST Search Check Images - 200
curl -s -X POST 'https://dge4e.wiremockapi.cloud/checks/images/search' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Checks API (2.1.1) · 9 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /checks/cancellations | Submit cancellation for a single check |
| GET | /checks/health | Retrieve health of service |
| POST | /checks/images/search | Retrieve check images |
| POST | /checks/issuances | Submit issuance for a single check |
| POST | /checks/prints | Submit Check Print request for processing |
| GET | /checks/prints/{id} | Get Check Print Details |
| POST | /checks/search | Retrieve check information |
| POST | /checks/stops | Create Stop Payment |
| POST | /checks/stops/revoke | Revoke Stop Payment |
Unauthenticated WireMock Cloud demo sandbox for Chase JPMorgan — not an official Chase JPMorgan sandbox, and it returns simulated example data only.
The Checks API's paper trail runs through one canonical instrument: check 1005, a paid customer check for $205.05 drawn in Chicago, payable to John Doe with ELITE CORP as second payee. Search returns it whatever criteria you send, and the image search returns its TIFF record — with the front and back fields holding the literal strings "base64encodedstringfront" and "base64encodedstringback", a fixture being honest about being one. The print flow is where the sandbox keeps real records: a print request answers 202 with a UUID minted per call, today's date as the issue date, both validation statuses at SUCCESS, and your submitted fields echoed back; the status read then serves exactly that stored record, down to the invocation id assigned at creation, while unknown print ids draw a structured Not Found. Issuance, stop payment, revocation, and cancellation each answer with their own fixed acknowledgment id.
No — the frontImage and backImage fields carry placeholder strings where base64 TIFF data would sit in production. That still verifies most of an imaging integration: request construction, the response envelope, pagination fields, and how image metadata is threaded to your viewer. The last step — decoding real image bytes — needs a private WireMock Cloud copy where you paste genuine base64 into the stub, which also lets you control file size for rendering tests.
Prints, and only prints. Each print request mints a distinct UUID and files a record the status route serves back — including whatever account number, check number, and amount you submitted — so the submit-then-poll loop is testable end to end, misses included via the structured 404. Issuance is the contrast: it always acknowledges with the same fixed id, and an issued check never surfaces in search. Treat issuance as a contract check and prints as the lifecycle rehearsal.
Deliberately, and worth encoding in your client: prints, stops, and revocations answer 202 because the bank processes them asynchronously; issuance answers 201 for a created resource; cancellation and every read answer 200. A client that treats anything other than 200 as failure — or assumes creation always means 201 — gets corrected here at no cost. The responses also carry a matched-stub-name header naming the stub that served them, useful when a test hits something unexpected.
The U.S. Bank Check Payables template is the library's stateful counterpart on the issuing side — created checks persist, updates merge, and deletion voids rather than erases. This Chase template's strength is breadth instead: the full verb set from issuance through stop, revoke, cancel, print, and imaging in one surface, with fixed acknowledgments that keep every route deterministic.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.