API template library

U.S. Bank Corporate Account Information mock API and live sandbox

A WireMock simulation of U.S. Bank's REST API — covering deposit, credit card, and loan account reporting — balances, transactions, statements, and ACH returns.

Vendor
U.S. Bank
Functionality
Balances, statements, transactions
Spec version
2.5.0
Endpoints
16
Stubs
16
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real U.S. Bank API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

US Bank Corporate Account Information

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://98we4.wiremockapi.cloud

GET Get Accounts

curl -s -X GET 'https://98we4.wiremockapi.cloud/accounts'

POST Get Current-Day Account Balances

curl -s -X POST 'https://98we4.wiremockapi.cloud/accounts/current-day' \
  -H 'Content-Type: application/json' \
  -d '{}'

POST Get Previous-Day Account Balances

curl -s -X POST 'https://98we4.wiremockapi.cloud/accounts/previous-day' \
  -H 'Content-Type: application/json' \
  -d '{}'
Method Path Summary
GET /accounts Get list of accounts for the authorized customer.
GET /accounts/{accountID}/balance Get good funds balance for one demand deposit account.
GET /accounts/{accountID}/statements Get deposit, credit card, trust, and loan account statements list.
GET /accounts/{accountID}/statements/{statementID} Get an account statement image.
GET /accounts/{accountID}/transactions/current-day Get transactions of an account for current-day.
GET /accounts/{accountID}/transactions/previous-day Get transactions of an account for prior business days over a date range.
POST /accounts/current-day Get account balances for an array of accounts for current-day.
POST /accounts/previous-day Get account balances for an array of accounts for previous-day.
POST /accounts/statements/requests Get a requestID for your statement generating request using async workflow.
GET /accounts/statements/requests/{requestID} Get binary PDF statement file using async workflow.
POST /accounts/transactions/ach-returns-and-noc/current-day Get ACH returns and NOC data for an array of accounts for current-day.
POST /accounts/transactions/ach-returns-and-noc/previous-day Get ACH returns and NOC data for an array of accounts for previous-day.
POST /creditcard-accounts Get Credit Card account balances for an array of accounts.
GET /creditcard-accounts/{accountID}/transactions Get transactions of a credit card account over a date range.
POST /loan-accounts Get loan account balances and summary for an array of accounts.
GET /loan-accounts/{accountID}/transactions Get transactions of a loan account over a date range.

Unauthenticated WireMock Cloud demo sandbox for U.S. Bank — not an official U.S. Bank sandbox, and it returns simulated example data only.

What's inside the Corporate Account Information template

Everything reports on one treasury persona: Arc Security Inc, banking at US Bank East Grand Forks, with a DDA carrying a good-funds balance just shy of $240 million. The detail runs deep in the direction treasury integrations actually need — transactions arrive with BAI type codes, SEC codes, and full ACH company detail down to the entry description; a dedicated route serves ACH returns and notifications of change; and the credit card summary demonstrates a partial-success pattern, pairing its 200 response with a warnings array flagging accounts that couldn't be fully reported. The path's account id is decorative — every route answers for whatever id you supply and reports the canonical account in the body.

  • Account roster — the entitlement-annotated list spanning DDA and credit card accounts, with data-retention terms
  • Balances — single-account good funds plus array-style current-day and previous-day summaries with ledger and float fields
  • Transaction reporting — current-day and previous-day activity, credit card and loan history, and the ACH returns-and-NOC feed
  • Statements — inline base64 statement images and the async request-then-fetch workflow

Frequently asked questions

A two-step handoff worth wiring tests around: the request route returns 202 with a requestID and IN_PROCESS status, and fetching that requestID returns a raw PDF-typed body rather than JSON. Client code learns to poll, then switch parsers for the binary leg — the exact seam where async document retrieval usually breaks.

They're drawn from the real vocabularies — a BAI code of 514 on an outgoing international wire, CCD as the SEC code on a corporate ACH entry, TAXPAYMENT as the entry description. Mapping tables and transaction-classification logic can be exercised against codes your production parser will genuinely meet.

As a partial success. The response is a 200 whose warnings array carries code 200.3202 for accounts that couldn't be fully provided — so treating any warning-bearing response as a failure, or ignoring warnings entirely, are both bugs this fixture is positioned to catch.

No — fromDate and toDate are accepted and the same fixture comes back, permanently dated 2020. Assertions belong on structure and code values, not on dates or row counts; range-boundary logic needs a private copy with stubs per window. The loan transaction route compensates with pageMeta landing on page 5 of 20, giving mid-stream pagination a real test case.

No — this API only watches the money. Opening cardholder accounts, changing limits, and lifecycle operations live in the Corporate Credit Cards template; the two together cover a corporate card program's write and read sides.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.