A WireMock simulation of U.S. Bank's REST API — covering credit card statement summaries and downloadable statement images.
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
GET Find statements
curl -s -X GET 'https://mjmq3.wiremockapi.cloud/accounts/your-accountUID/statements'GET Get statement image (PDF)
curl -s -X GET 'https://mjmq3.wiremockapi.cloud/accounts/your-accountUID/statements/your-imageDate'Spec catalog — Corporate Statements (1.2.0) · 2 endpoints
| Method | Path | Summary |
|---|---|---|
| GET | /accounts/{accountUID}/statements | Get statement summaries. |
| GET | /accounts/{accountUID}/statements/{imageDate} | Retrieve (download) a statement image. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Two routes form the find-then-fetch chain every statement feature implements: a summary list reporting current and previous cycle balances, payment due dates, and per-statement fee breakdowns, and an image route that delivers the statement document itself — a genuine application/pdf response whose body opens with %PDF-1.4. The summary fixture is populated schema-first: every monetary field reads 250.5 and every cycle date 1111-11-11, so each of the dozen fee and balance fields is present for mapping while the uniform values discourage arithmetic assertions. The exception is the field the chain turns on — downloadImageDate, 2024-01-31 — which is exactly the value the image route's path expects to receive.
It's a shape catalog, not a ledger. The fixture's job is to put every field the schema defines in front of your deserializer at once — balances, fees, cash advances, payment records — and the sentinel values are a guard rail: totals computed from them are obviously meaningless, which steers tests toward structural assertions. The one field carrying a plausible value, downloadImageDate, is the one the workflow actually consumes.
Thirty-three bytes that are nonetheless a real PDF response: correct content type, correct magic bytes, no JSON envelope in sight. That's enough to prove a client switches decoding modes mid-API, streams the document to disk or browser, and doesn't try to parse it as text. Note the route answers for any date in the path, not just the advertised one — the not-found case for a missing statement month is a stub to add in your own copy.
The path segment isn't consulted — every account id yields the same summary, whose body reports the canonical sixteen-digit expandedLimitAccountUID regardless. Multi-account statement screens can still be driven from it: iterate your account list, call per account, and assert the rendering; per-account variation is private-copy work. In the real product, the UID would come from the card-management side — the Corporate Credit Cards template models the account setup that mints it.
Scope and delivery. This API is the credit card statement archive — cycle summaries plus a synchronous, GET-a-PDF download. The Corporate Account Information template reports on deposit and loan accounts too, and its document retrieval is asynchronous: request an id, poll, then fetch. Integrations covering both surfaces get to test the same "show me the statement" feature against two genuinely different retrieval contracts.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.