A WireMock simulation of U.S. Bank's REST API — covering shipment orders, invoices, eBills, supporting documents, and call-for-funds reporting.
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 Search transaction documents
curl -s -X POST 'https://dgd7v.wiremockapi.cloud/transactions/search' \
-H 'Content-Type: application/json' \
-d '{}'GET Get attachment by ID
curl -s -X GET 'https://dgd7v.wiremockapi.cloud/transactions/attachments/your-attachmentID'PUT Update order
curl -s -X PUT 'https://dgd7v.wiremockapi.cloud/orders/your-BOLNumber' \
-H 'Content-Type: application/json' \
-d '{}'Spec catalog — Freight Payment Transactions (1.4.0) · 13 endpoints
| Method | Path | Summary |
|---|---|---|
| POST | /accounts/search | Find the accounts associated with the Freight Payment Key (customer ID). |
| POST | /call-for-funds/search | Find the call-for-funds for Shipper Bill-To accounts. |
| POST | /ebills | Submit a new eBill for processing. |
| POST | /invoices | Submit a new Invoice for processing. |
| PUT | /invoices/{InvoiceNumber} | Update an existing invoice. |
| POST | /invoices/{InvoiceNumber}/cancel | Cancel an existing invoice. |
| POST | /orders | Create a new shipment order for processing. |
| PUT | /orders/{BOLNumber} | Update an existing shipment order. |
| POST | /orders/{BOLNumber}/cancel | Cancel an existing shipment order. |
| POST | /transactions/attachments | Add (upload) documents or file to a your freight order, invoice, or invoice. |
| GET | /transactions/attachments/{attachmentID} | Retrieve (download) supporting document. |
| POST | /transactions/attachments/search | Look up freight transaction supporting documents. |
| POST | /transactions/search | Document identifier retrieves the freight transaction documents. |
Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.
This is the intake side of U.S. Bank's freight audit-and-pay system, where shippers submit orders and carriers submit invoices, and the mock speaks its asynchronous dialect throughout: every document submission — order, invoice, eBill, update, cancel — returns 202 with a document number and nothing else, because processing happens downstream in the freight network. The document search then shows what downstream looks like, returning a freight document whose financial status is AE, Audit Exception, detailed as "Stale Dated Invoice" — a payment held up by audit, which is precisely the state freight-payment integrations exist to detect and resolve. Account and call-for-funds fixtures come straight from the product's regression environment, complete with a buyer billing in AED.
Because acceptance and processing are separate events in freight payment — the API's job ends at intake, and audit results surface later through search. Clients built here learn the right discipline: persist the returned BOL or invoice number, treat 202 as "received" rather than "approved", and poll the transaction search for financial status.
The unhappy middle of the payment lifecycle. The search fixture's status block carries the code, the human-readable name, and a stale-dated-invoice detail with its timestamp — enough to drive exception queues, status badges, and the reconciliation logic that decides which held payments need human attention.
Shared fixture, and a hint at the domain: an eBill is an invoice variant in this system, and both intakes acknowledge with the same canonical document number the search fixture then references as both invoiceNumber and ebillNumber. Assertions should treat document numbers as opaque references joined by search, not as per-route unique keys.
Metadata, in both directions. Upload acknowledges with a fixture filename rather than storing your bytes, and retrieval returns a JSON envelope — chargeable weight, cubic feet, detention dates — instead of file content. That covers the bookkeeping around freight evidence; byte-level upload and download handling needs stubs of your own.
The fixtures were recorded from the freight platform's regression data, where "Regression Buyer Co 1" pays on a daily cycle in UAE dirhams with one day to pay and fourteen to appear. Multi-currency code paths get a non-USD case by default — and the naming is a useful reminder that the roster is test-world data, not a customer directory to assert against.
Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.