A WireMock simulation of U.S. Bank's REST API — covering card issuance, lost-stolen replacement, suspensions, temporary limits, and shipment tracking.
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 Create card
curl -s -X POST 'https://eml44.wiremockapi.cloud/cards' \
-H 'Content-Type: application/json' \
-d '{}'PUT Update temp limits
curl -s -X PUT 'https://eml44.wiremockapi.cloud/cards/temp-limits/update' \
-H 'Content-Type: application/json' \
-d '{}'POST Update card
curl -s -X POST 'https://eml44.wiremockapi.cloud/cards/update' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Voyager Account Management - Cards (1.7.0) · 17 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /cards | Create a card. |
| POST | /cards/cancel | Cancel a card. |
| POST | /cards/card-shipments/read | Return card shipment details. |
| POST | /cards/card-shipments/search | Search for card shipments within a time-range. |
| POST | /cards/comments | Log a card comment. |
| POST | /cards/comments/delete | Delete a card comment. |
| POST | /cards/lost-stolen | Report a card as lost or stolen, and issue a new card. |
| POST | /cards/read | Return details of a card. |
| POST | /cards/replace | Replace a worn or damaged card. |
| POST | /cards/reset-pin-entry | Unlock PIN entry for a card. |
| POST | /cards/search | Find unexpired cards. |
| POST | /cards/suspend | Suspend a card. |
| POST | /cards/temp-limits/delete | Delete card temporary limits. |
| POST | /cards/temp-limits/read | Read card temporary limits. |
| PUT | /cards/temp-limits/update | Update card temporary limits. |
| POST | /cards/unsuspend | Unsuspend a card. |
| POST | /cards/update | Update a card. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Card issuance here is a working loop: each create mints a six-digit card number, and the read route — a POST keyed on the cardID in your request body, in Voyager style — resolves exactly the numbers this sandbox has issued, reporting them as ISSUED. Around it, the servicing fixtures are unusually specific. The lost-stolen route retires card 654321 and hands back 654322, the id arithmetic of a reissue made visible. The temporary-limits read is the richest body in the template: transaction counts and dollar amounts tiered by day, week, month, and cycle, restricted to MON-FRI within a 09:00-to-17:00 UTC window — a fleet manager's working-hours policy rendered as data.
They're separate populations. The search, shipment, and lost-stolen fixtures all describe roster card 654321, but the read store only contains numbers minted through create — ask it about 654321 and you get the card-does-not-exist envelope. Flows that chain search-then-read need a private copy where the two are wired together; here, chain create-then-read instead.
Schedule-shaped policy. Most limit fixtures stop at amounts; this one layers count and dollar ceilings across four periods, then binds them to weekdays and a working-hours window with a second, empty time range beside the active one. Renderers and validators for time-boxed controls get every branch — populated range, empty range, day-of-week mask — from a single response.
A commentID that is literally an ISO-8601 timestamp rather than an opaque token. Treat it as an identifier all the same — code that parses ids for meaning breaks when the real system changes format, so the fixture rewards clients that keep ids opaque. The delete route accepts the same value to retire the note.
Lost-stolen is the security path — it returns 201 with the old and new card numbers side by side, modeling a compromised card leaving the fleet and its successor arriving. Replace is the wear-and-tear path and simply acknowledges with 204, no new number issued. Client flows should assert on that asymmetry rather than expecting both to mint.
The Voyager Accounts template — account setup, organization hierarchy, and the Voyager+ limit and product catalogs live there, and its pages explain the same POST-for-everything convention this API follows. Drivers, vehicles, and transaction search each get their own sibling template in the Voyager family.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.