A WireMock simulation of U.S. Bank's REST API — covering cardholder account setup, credit limits, merchant controls, and card lifecycle operations.
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 CH Account setup
curl -s -X POST 'https://g8z49.wiremockapi.cloud/accounts/setup' \
-H 'Content-Type: application/json' \
-d '{}'PATCH Update auth limits
curl -s -X PATCH 'https://g8z49.wiremockapi.cloud/accounts/your-accountUID/auth-limits' \
-H 'Content-Type: application/json' \
-d '{}'PUT Update address
curl -s -X PUT 'https://g8z49.wiremockapi.cloud/accounts/your-accountUID/addresses' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Corporate Credit Cards (1.2.3) · 20 endpoints
| Method | Path | Summary |
|---|---|---|
| GET | /accounts/{accountUID} | Read account details. |
| POST | /accounts/{accountUID}/activate | Activate the card associated with this account. |
| GET | /accounts/{accountUID}/addresses | Read account addresses. |
| PUT | /accounts/{accountUID}/addresses | Update account address. |
| GET | /accounts/{accountUID}/auth-limits | Read the authorization limits for an account. |
| PATCH | /accounts/{accountUID}/auth-limits | Change the account authorization limits. |
| GET | /accounts/{accountUID}/credit-limit | Read credit limit details for an account. |
| PATCH | /accounts/{accountUID}/credit-limit | Change the credit limit. |
| GET | /accounts/{accountUID}/cvv | Get CVV security code. |
| GET | /accounts/{accountUID}/merchant-auth-controls | Read the list of merchant authorization controls for an account. |
| PUT | /accounts/{accountUID}/merchant-auth-controls | Replace the list of merchant authorization controls. |
| GET | /accounts/{accountUID}/owner | Get account owner details. |
| PATCH | /accounts/{accountUID}/owner | Update account owner information. |
| GET | /accounts/{accountUID}/realtime-credit-details | Read the most current limits, availablility, and balances. |
| POST | /accounts/{accountUID}/replace | Request a card replacement. |
| GET | /accounts/{accountUID}/status | Read account status. |
| PUT | /accounts/{accountUID}/status | Update account status. |
| POST | /accounts/search | Search for card accounts. |
| POST | /accounts/setup | Create a cardholder account. |
| GET | /accounts/setup/{setupID} | Read the setup status associated with a create-account request. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
The mock is organized around one fully-drawn cardholder account, and the async setup flow is the front door to it: POST /accounts/setup returns 202 with a setupID, and polling the setup-status route yields SETUP_COMPLETED alongside the account UID every other route is keyed to. Read that account and you get the whole corporate card picture — owner Jon Doe with work, personal, fax, and postal contact details, a five-level processing hierarchy of bank, agent, company, division, and department codes, and a status of V9-VoluntarilyClosed. Substitute any other UID and the account family of routes answers with the numbered resource-not-found envelope, which is exactly the wrong-id behavior an employee card-management app has to survive.
From the setup-status response — its statuses array carries the ID and UID of the completed account, and that UID is the key the detail, owner, credit-limit, and status routes are matched on. Client code that chains setup → poll → first account read therefore works unmodified; hard-coding any other account number gets you the 404 path instead.
The fixture ships with status V9-VoluntarilyClosed — a prefixed status code from the card processor's vocabulary, not a plain enum. It's a productive default: dashboards must render the human-readable part, and card-action screens must decide which operations a closed account still permits. The activate and replace verbs acknowledge with 204 either way, without rewriting the stored status.
Two: the CVV route hands back its three-digit code for any account id, and real-time credit details reports limits and balances the same way. Both are deliberate conveniences — security-code display and available-credit widgets can be tested without first walking the setup flow.
It's useful, whatever the intent: the response carries pageMeta with both previous and next links populated and a total of 115 accounts across 6 pages, so pagination code gets a middle-of-the-walk case — the one where both directions must render — rather than the easier first-page case most fixtures give you.
In the reporting product. The Corporate Account Information template serves credit card summaries, transaction history, and statement images across account types; this template owns the card lifecycle itself — creating cardholders, moving limits, and controlling where the card may be used.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.