A WireMock simulation of U.S. Bank's REST API — covering partner-published event notifications into U.S. Bank.
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 Publish webhook events
curl -s -X POST 'https://lo2d6.wiremockapi.cloud/events' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Incoming webhooks (1.0.0) · 1 endpoint
| Method | Path | Summary |
|---|---|---|
| POST | /events | Event notifications from Partners. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
This template inverts the usual direction of webhook testing. The API it simulates is U.S. Bank's own event-ingestion endpoint — the address a partner application publishes notifications to — which means the mock stands in for infrastructure you could never point a test suite at otherwise: someone else's receiver. POST an event to /events and a bodyless 200 comes back, for an empty object and a fully-formed notification alike. Receipt is the entire response contract, and everything interesting under test lives on your side of the wire: event serialization, delivery, and what your publisher does with an acknowledgment that carries no payload.
The receiver that isn't yours. In this integration U.S. Bank is the consumer — partners push events to the bank — so the component that needs testing is your outbound pipeline: the code that builds the notification, signs and sends it, and reacts to the acknowledgment. Pointing that pipeline here lets delivery logic run end-to-end in CI without a partner-environment credential or a real bank endpoint in the loop.
The status line — and that your client is comfortable with it. An empty 2xx is a legitimate ingestion acknowledgment, and HTTP clients configured to deserialize every response into a model object throw on it, which is a genuine bug class this stub surfaces immediately. Assert the request you sent instead: correct route, correct content type, a payload that round-trips through your own serializer.
No — an empty object is received as gracefully as a complete notification, because the public stub matches the route, not the schema. Rejection paths are private-copy work, and simple work: a WireMock Cloud copy can match on required fields and answer 400 for anything missing them, and its request log doubles as the assertion surface — each event your pipeline published is there to inspect, payload and headers included.
The ones where U.S. Bank notifies the partner. The Avvance Connect template carries a notification-status surface for its point-of-sale financing flow, and the Instant Payments template models requests for payment arriving over the RTP network. Between those and this intake, both halves of an event-driven bank integration have a mock to build against.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.