A WireMock simulation of U.S. Bank's REST API — covering purchase order detail and search, card transaction detail, and transaction attachments.
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 Get Transaction by ID
curl -s -X GET 'https://y0zyv.wiremockapi.cloud/transactions/your-transactionID'POST Search Orders
curl -s -X POST 'https://y0zyv.wiremockapi.cloud/orders/search' \
-H 'Content-Type: application/json' \
-d '{}'GET Get Transaction Attachment
curl -s -X GET 'https://y0zyv.wiremockapi.cloud/transactions/your-transactionID/attachments'Spec catalog — Access Online Transactions and Orders (1.1.1) · 4 endpoints
| Method | Path | Summary |
|---|---|---|
| GET | /orders/{orderID} | Retrieve order details. |
| POST | /orders/search | Find orders matching the search criteria. |
| GET | /transactions/{transactionID} | Retrieve transaction details. |
| GET | /transactions/{transactionID}/attachments | Retrieve transaction attachment. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Access Online is U.S. Bank's commercial-card program portal, and this API is its data window: the purchase orders a program administrator raises and the card transactions that settle against them. Both detail reads reflect whatever id the path carries into a fully populated record, so client flows never stall hunting for a magic identifier. The order fixture is a purchase order at line-item depth — quantities in pounds, unit costs, percent-fulfilled tracking, custom key-value fields, and the list of card transactions attached to it — while the transaction fixture answers with cycle dates, a dispute block, and the bank-through-department coding hierarchy this card platform hangs every record on. The attachment route ends the chain with an actual PDF, served raw: bytes beginning %PDF, not a JSON wrapper around a link.
The response's page block emits its number field with no value at all, so the document is syntactically invalid even though the HTTP layer reports success — and it does so for every request variation. It's a sharper failure mode than an honest 500: only clients that validate parses independently of status codes classify it correctly. Search-backed features need a private WireMock Cloud copy with a corrected stub; the two order records visible in the raw body are usable reference data for writing it.
Use any id that fits your test's naming scheme — the detail routes echo the path id into the response's identifier field and attach the canonical record to it. That inverts the usual sandbox discipline: there is no not-found branch to exercise here, and tests should assert that the id round-trips plus whatever record structure they consume, not that unknown ids fail.
Material. The transaction's MCC group says AIRLINE while the MCC itself is 7276, tax preparation services — two classification levels that genuinely drift apart in card processing when group tables lag code updates. Spend-category logic keyed to one level will disagree with logic keyed to the other, and this fixture is positioned to expose which level your reporting actually trusts.
That your client handles a binary body on an otherwise-JSON API: the route returns a small, structurally valid single-page PDF as raw bytes. Content-negotiation code, download handlers, and virus-scan hooks get real material without a base64 detour. The account coding on these records — bank, agent, company, division, department — is the same five-level hierarchy whose card-management side lives in the Corporate Credit Cards template, making the pair natural companions for program-administration testing.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.