A WireMock simulation of U.S. Bank's REST API — covering FX rate quotes, quote acceptance, and settlement-date lookups for currency pairs.
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 Start FX quote
curl -s -X POST 'https://81l8q.wiremockapi.cloud/quotes' \
-H 'Content-Type: application/json' \
-d '{}'POST Get settlement date
curl -s -X POST 'https://81l8q.wiremockapi.cloud/settlement-date' \
-H 'Content-Type: application/json' \
-d '{}'POST Get all settlement dates
curl -s -X POST 'https://81l8q.wiremockapi.cloud/all-settlement-dates' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Foreign Exchange API (1.1.0) · 4 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /all-settlement-dates | Retrieve a list of settlement dates for a currency pair/symbol. |
| POST | /quotes | Start an FX quote and retrieve the rate for a given currency pair. |
| POST | /quotes/accept | Accept a rate for a given currency pair using a quoteId. |
| POST | /settlement-date | Retrieve a Settlement Date for a currency pair and specific settlement type. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
The template's core is the two-step dance every FX integration performs: request a rate, then commit to it before it expires. A quote request mints a fresh ECTESTWIRE-prefixed quoteId into a tradeable EURUSD spot quote at 1.163273, stamped with a validity window exactly five minutes wide. Acceptance is gated on that mint: quote an id the sandbox issued and the deal fills — dealNumber assigned, your quoteId echoed back as the clOrdId in FIX style, and a "London payroll" memo revealing the fixture's scenario — while an id it never issued draws the quote-not-found-or-expired error. Around the dealing flow sit the calendar routes: a single settlement date for a pair, and the full settlement-date list with a noon cutoff, a cash-not-allowed flag on CNY, and a tenor labeled YESTERDAY.
Yes — this is one of the sandboxes where the sequence is enforced. The accept route recognizes only quoteIds this environment has issued; an invented id, or none at all, gets the numbered quote-not-found error. That makes the quote-then-accept chain, including the failure branch for stale or fabricated ids, testable end to end without any seeding.
The fill response includes statusRejectReason UNKNOWN_SYMBOL beside quoteStatus FILLED — a reason field populated even when nothing was rejected. Trading integrations meet this in real FIX-adjacent APIs, where reason codes are structural rather than conditional: read the status first and consult the reason only when the status says to. Code that alerts on any non-empty reject reason will false-alarm here, by design.
It's the calendar's way of expressing back-valued settlement, and the list fixture leads with it — a settlement type most client enums forget, dated in the past relative to the trade. Date logic that assumes settlement is always today-or-later trips on it immediately, which is a cheaper place to learn that than a production reconciliation break.
Not in this API — dealing ends at the deal number, and the funds travel on a payment rail. The natural companion is the Wire Transfers template, whose international route models the cross-border leg an FX deal typically funds; run the two sandboxes together to rehearse a quote, fill, and wire sequence with consistent test choreography.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.