A WireMock simulation of U.S. Bank's REST API — covering FDX-standard account data, transactions, statements, tax documents, and capability discovery.
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 account list
curl -s -X GET 'https://1k7q3.wiremockapi.cloud/account-list'POST Get account (POST form)
curl -s -X POST 'https://1k7q3.wiremockapi.cloud/account' \
-H 'Content-Type: application/json' \
-d '{}'GET Get account by ID
curl -s -X GET 'https://1k7q3.wiremockapi.cloud/account/your-accountId'Spec catalog — Data Toolbox (FDX API) (3.1.2) · 17 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /account | Get account details for an account. |
| GET | /account-list | Get summary of all accounts for the current token. |
| GET | /account/{accountId} | Get account details for an account. |
| GET | /account/{accountId}/statement/{statementId} | Get an account statement image. |
| GET | /account/{accountId}/statements | Get account statements list. |
| GET | /account/{accountId}/tax/{taxDocumentId} | Get a tax document image for an account. |
| GET | /account/{accountId}/taxes | Get tax documents list for an account. |
| GET | /account/{accountId}/transactions | Get account transactions. |
| POST | /account/statement | Get an account statement image. |
| POST | /account/statements | Get account statements list. |
| POST | /account/taxes | Get tax documents list for an account. |
| POST | /account/transactions | Get account transactions. |
| GET | /accounts-details | Get account details for an array of accounts. |
| POST | /accounts-details | Get account details for an array of accounts. |
| GET | /availability | Get information about this API's availability. |
| GET | /capability | Get information about this API's capabilities. |
| GET | /customer | Get customer information within the authorization scope. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Data Toolbox is U.S. Bank's implementation of the Financial Data Exchange v3 standard — the interface a data aggregator codes against to pull consumer-permissioned banking data — and the template mirrors its distinctive architecture. Most reads exist twice, as a token-scoped GET and a POST accepting an account array, and both verbs answer here. The discovery endpoints are modeled too: capability reports support flags for customer, accounts, transactions, statements, images, bill pay, and transfer, the handshake an aggregator performs before deciding what to sync. Fixture values are largely the spec's own placeholders, with one pointed exception — the transactions route serves a posted $12.50 point-of-sale debit, categorized Shopping and Dining, memo "Coffee shop", dated and referenced like production data.
The stubs were generated from the FDX specification's own examples, placeholders included. Structure, nesting, and enum-bearing fields like accountType CHECKING and status OPEN are all faithful, so deserialization and shape assertions work; display-layer tests that want plausible balances and names should lean on the transactions route or seed a private copy with curated values.
Either — and the mock is a safe place to settle the choice. FDX deployments differ on whether account detail is fetched by GET with the id in the path or POST with ids in the body; this sandbox accepts both against the same data, letting you exercise whichever convention your target institutions require without changing environments.
JSON with a pageContent field holding placeholder text — not PDF bytes and not an FDX binary stream. It anchors the retrieval contract (ids in, document envelope out) while leaving binary-handling untested; pair it with stubs serving real base64 content in a WireMock Cloud copy when the rendering path matters.
No — production Data Toolbox sits behind consumer consent and OAuth-based authentication, and the mock strips that layer so the data plane is reachable immediately. Consent-flow UI and token lifecycle handling need their own simulation; what's here is everything that happens after authorization succeeds.
Opposite ends of the same standard. The Plaid FDX template models the network's recipient directory — who receives data — while Data Toolbox models a bank actually serving FDX data: accounts, transactions, documents. An aggregator integration touches both shapes, and the pair covers it.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.