A WireMock simulation of U.S. Bank's REST API — covering the bank-holiday calendar and single-date holiday checks.
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 Date check - is a bank holiday
curl -s -X GET 'https://jyk9y.wiremockapi.cloud/bank-holidays/date-check?date=2025-01-01'GET List bank holidays
curl -s -X GET 'https://jyk9y.wiremockapi.cloud/bank-holidays'GET Date check - not a bank holiday
curl -s -X GET 'https://jyk9y.wiremockapi.cloud/bank-holidays/date-check'Spec catalog — Bank Holidays API (1.2.0) · 2 endpoints
| Method | Path | Summary |
|---|---|---|
| GET | /bank-holidays | List of bank Holidays for the US Bank. |
| GET | /bank-holidays/date-check | This API will validate if the date passed in the request is a bank holiday and returns value as Yes/No. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
The calendar this template serves is not invented test data — its fourteen entries are the genuine Federal Reserve observance schedule, from New Year's Day 2025 through Presidents Day 2026, Juneteenth and Indigenous Peoples' Day included. Settlement-date calculators, SLA clocks, and payment schedulers therefore compute against dates their production counterparts will actually observe. Each entry arrives as a bare local datetime — midnight, no timezone offset — and the companion date-check route answers the yes/no question a scheduler asks on its way to picking an execution day. Both verdicts are reachable: January 1st 2025 confirms as a holiday, and every other date comes back negative.
They're accepted and disregarded — the full fourteen-date roster returns whether you ask for one year, a six-month window, or nothing at all. The spec's contract (a two-year default, an end date capped five years out) is documentation here, not behavior, so windowing logic needs a private WireMock Cloud copy with one stub per query shape. Against the public instance, assert on the roster itself.
The two routes don't consult each other. The affirmative verdict is bound to one exact query — date=2025-01-01 — and every other value, roster dates included, falls through to the negative stub. That gives you both branches of the check cheaply, but it also means list-then-verify flows will catch the two routes disagreeing. Consistency between the calendar and the check is yours to wire up in a private copy.
Possibly trouble, usefully so. Entries render as 2025-01-01T00:00:00 — a time component with no zone designator — so a parser that insists on a Z or offset rejects the feed, and date-equality logic that compares full timestamps must truncate first. Both are decisions holiday-aware code has to make anyway; this fixture forces them before an integration test does.
Anywhere money moves on a schedule. The PaySmart template acknowledges transfers with a cutoff-passed warning that defers processing to the next business day — precisely the day this calendar defines — and the Instant Payments template models the RTP and FedNow rails that settle around the clock, holidays notwithstanding. Testing rail-selection logic against all three gives the business-day question real coverage.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.