A WireMock simulation of U.S. Bank's REST API — covering fleet account setup, card mailing addresses, organization hierarchies, and Voyager+ limits, types, and products.
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 account
curl -s -X POST 'https://3r78z.wiremockapi.cloud/accounts' \
-H 'Content-Type: application/json' \
-d '{}'POST Read account
curl -s -X POST 'https://3r78z.wiremockapi.cloud/accounts/read' \
-H 'Content-Type: application/json' \
-d '{}'POST Update account
curl -s -X POST 'https://3r78z.wiremockapi.cloud/accounts/update' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Voyager Account Management - Accounts (1.6.0) · 22 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /accounts | Create an account. |
| POST | /accounts/card-addresses | Create (add) a card address. |
| POST | /accounts/card-addresses/delete | Delete a card address. |
| POST | /accounts/card-addresses/read | Retrieve a card address. |
| POST | /accounts/card-addresses/search | Find all card addresses for an account. |
| POST | /accounts/card-addresses/update | Update 1 or more card address fields. |
| POST | /accounts/close | Close an account. |
| POST | /accounts/read | Return details of an account. |
| POST | /accounts/search | Find accounts within an org-level hierarchy. |
| POST | /accounts/suspend | Suspend an account. |
| POST | /accounts/unsuspend | Unsuspend an account. |
| POST | /accounts/update | Update an account. |
| POST | /organizations | Create an organization. |
| POST | /organizations/search | Find all organizations within an org-level hierarchy. |
| POST | /voyager-plus/card-limits | Create (add) a card limit. |
| POST | /voyager-plus/card-limits/search | Find all card limits for an account. |
| POST | /voyager-plus/card-limits/update | Update 1 or more card limit fields. |
| POST | /voyager-plus/card-types | Create (add) a card type. |
| POST | /voyager-plus/card-types/read | Retrieve a card type. |
| POST | /voyager-plus/card-types/search | Find all card types for an account. |
| POST | /voyager-plus/card-types/update | Update 1 or more card type fields. |
| POST | /voyager-plus/products/search | Find all product types. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
Voyager's account layer follows the fleet-processor idiom of doing everything by POST — reads and searches included — and any client that survives here has that verb discipline right. The anchor fixture is fleet account 876543210, name ACME, type Fleet: account create hands its id back regardless of what you submit, the read route serves it, and the card-address routes attach address 000109 to it. The Voyager+ family tells its story on a second account, 897654321, where card limits and card types carry product codes and effective timestamps. Between the two sit the deliberately empty rosters — account, organization, and product searches return bare arrays, the zero-results case most search UIs meet in production before they meet any other.
Because the real Voyager API works that way: retrieval routes are /accounts/read and /accounts/search, taking their keys in the request body rather than the path. The mock preserves the convention, so an integration built on RESTful GET assumptions fails here before it fails in certification — which is the point.
Empty states, mostly. Account, organization, and Voyager+ product searches all return well-formed responses with zero rows, making this the natural place to verify no-results rendering, empty-state messaging, and that pagination controls stay quiet when there's nothing to page. Card-address, card-limit, and card-type searches return single-row rosters for the opposite case.
The base account routes speak in terms of 876543210, while the Voyager+ card-limit and card-type bodies belong to 897654321. Cross-referencing code that joins Voyager+ data onto account reads should therefore key on the response fields, not assume a single id threads the whole template — or stub the join explicitly in a private copy.
No — create is a fixed acknowledgment, always answering with the ACME account's id no matter the payload. Tests should treat it as a contract check on request/response shape. For a fleet store where created records genuinely accumulate and round-trip, the One Card for Fleet template is the U.S. Bank surface built that way.
In their own template — Voyager splits account administration from card operations. Issuance, lost-stolen reissue, temporary limits, and shipment tracking are the Voyager Cards template's territory, with drivers, vehicles, and transactions each modeled as further siblings in the family.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.