A WireMock simulation of U.S. Bank's REST API — covering account rosters, transfer initiation between U.S. Bank hosted accounts, and transfer history.
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 List accounts
curl -s -X GET 'https://kv6j0.wiremockapi.cloud/accounts'Spec catalog — Account Transfers (1.1.0) · 4 endpoints
| Method | Path | Summary |
|---|---|---|
| GET | /accounts | Get list of accounts for the authorized customer. |
| POST | /transfers | Initiate account transfer between U.S. Bank hosted accounts. |
| POST | /transfers-history | Retrieve tranfers list/history by passing in criteria such as transaction status and a date range. |
| GET | /transfers/{paymentID} | Retrieve Processed transfer details. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
The account roster is the load-bearing fixture. Three Arc Security Inc accounts return from a single GET, and the trio is built as a permissions exercise: the primary DDA moves money in both directions, the Operating account is flagged DEBIT-only, and the Reserve account CREDIT-only — so a transfer-form UI has everything it needs to test that source and destination pickers respect debitCreditIndicator, from one response. Arc Security is the same treasury persona whose balances and transactions the reporting sandbox serves, which keeps multi-API test scenarios coherent. The movement routes themselves are a different story, told honestly in the FAQ below: both the transfer intake and the history search fail in rendering and return 500s, making this template's public sandbox a roster-and-error-path surface rather than an end-to-end transfer simulator.
Their response templates fail while rendering — the engine reports the base JSON it tried to transform as an empty string and emits the error into the body — and no request shape changes the outcome. Treat both routes as unavailable in the public sandbox: exercising initiation and history properly means a private WireMock Cloud copy where those two stubs are replaced with responses you control.
It does, and the trace is instructive: each attempt registers a record in the shared store, and the history route's item count grows accordingly even though every item then fails to render. That's worth knowing purely so the growing count doesn't read as your test suite's bug — the store accumulates from all visitors' attempts until it resets.
No — because initiations never return a parseable id, there is nothing to quote back, and every id tried draws the gateway's URI-not-found envelope, code 404.0001.4001. What that leaves genuinely testable is the miss branch: clients get a well-formed numbered error body with a help link to assert against, which is the response shape they'll see in production for expired or foreign ids.
The persona threads through the vendor's reporting surface: Arc Security Inc, its East Grand Forks DDA, and the adjacent account numbers all reappear with balances, BAI-coded transactions, and statements in the Corporate Account Information template. Pairing the two lets an integration list accounts here and report on the same accounts there without inventing bridge data.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.