A WireMock simulation of U.S. Bank's REST API — covering fund entities, accounting calendars, NAV and rate-of-return reporting, trial balances, holdings, and tax lots.
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 institutional URL
curl -s -X GET 'https://5e7mz.wiremockapi.cloud/url'POST Get holdings details
curl -s -X POST 'https://5e7mz.wiremockapi.cloud/entities/holdings' \
-H 'Content-Type: application/json' \
-d '{}'GET Get entity list
curl -s -X GET 'https://5e7mz.wiremockapi.cloud/entities'Spec catalog — Investment Accounting (1.0.0) · 8 endpoints
| Method | Path | Summary |
|---|---|---|
| GET | /entities | Get the list of all entities (custody accounts and funds) associated with the client. |
| GET | /entities/{entityId}/calendar | Get accounting calendar for an entity. |
| GET | /entities/{entityId}/nav-netassets-sharesoutstanding | Get NAV, net assets and shares outstanding for an entity. |
| GET | /entities/{entityId}/returns | Get the rate of return for an entity. |
| GET | /entities/{entityId}/trialbalance | Get trial balance for an entity. |
| POST | /entities/holdings | Get holdings for an entity. |
| POST | /entities/taxlot | Get taxlot details for an entity. |
| GET | /url | getInstitutionalUrl |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
One fund anchors the template: CanaFund, an active entity fed from Eagle, the accounting platform named in every response's source field. Whatever entityId your request paths carry, the answers describe CanaFund — the roster has a single row, and the sub-resource routes report against it unconditionally. Depth varies deliberately by route. The trial balance is fully valued: an escrow account opening at $35,000.20, the period's debits and credits, and a classification block sorting the position into assets, inventory, and a long exposure. Holdings and tax lots describe a genuinely production-shaped security — a Peak Technologies senior secured term loan carrying CUSIP, ISIN, ticker, exchange, and a 6.125% rate — while NAV and returns serve the full response skeleton with placeholder values inside.
The books and the positions. Trial-balance amounts, the term loan's identifiers, and its 6.125% rate are concrete enough to drive display and mapping logic, and the taxlot route adds a purchase date to the same security. Valuation is the opposite: NAV, net assets, shares outstanding, and every cell of the rate-of-return grid contain the specification's placeholder text, so those routes verify parsing and nothing else — the same generated-from-spec character parts of the Data Toolbox template show.
It renders the product's full reporting matrix: cumulative returns at horizons from one day out past a year, each in a load and a no-load variant. Client models that flatten this grid — or pick three horizons and ignore the rest — get their field mapping checked against every key the real API can emit, which is most of the route's value while the numbers stay placeholder.
No — CanaFund answers for all of them, and no id produces a not-found error anywhere in the template. Multi-fund behavior (and missing-fund error handling) must be stubbed in a private WireMock Cloud copy; the public sandbox's job is the response vocabulary of each accounting surface, not fund lookup.
The real API takes their filter criteria — as-of dates, asset scopes — in a request body, so the routes are POSTs by design and the mock keeps the verbs faithful. A client generated from the spec exercises both verb styles in one integration, and the institutional-URL route rounds out the survey by returning a bare JSON string, the template's smallest well-formed response.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.