Western Alliance Bank
Western Alliance Bancorporation (NYSE: WAL) is a Phoenix, Arizona based super-regional bank holding company with roughly $80 billion in assets, operating through its principal subsidiary Western Alliance Bank, an Arizona state-chartered commercial bank and member FDIC that runs regional divisions including Alliance Bank of Arizona, Bank of Nevada, Bridge Bank, and Torrey Pines Bank. It is a commercial- and business-banking focused institution rather than a consumer neobank. Western Alliance runs a real first-party developer portal, the WAB API Developer Portal ("Developer Hub") at developer.westernalliancebank.com, exposing commercial Treasury Management open-banking APIs for balance and transaction information, check images, funds transfers, and stop payments. Access is partner/customer-gated: API specifications are downloaded from the Developer Hub only with WAB-issued credentials, and authentication uses OAuth2 client-credentials (Client ID, Client Secret), a Client Certificate (mTLS), and access tokens across UAT and Production environments. Its APIs are also reachable through payment-platform partners such as Modern Treasury. No public consumer FDX or CFPB Section 1033 data-access API is documented, and no OpenAPI/Swagger is publicly downloadable.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Western Alliance Bank the way a machine reads it — 3 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Western Alliance Bank scores 29.1/100 (emerging), with a separate agent-readiness read of 14/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Western Alliance Bank
Each block below is one kind of artifact we hold for Western Alliance Bank. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Western Alliance Bank API (Treasury Management)
Western Alliance Bank's commercial open-banking API lets approved business clients interact directly with WAB systems to access balance and transaction information, retrieve che...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Western Alliance Bank — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/western-alliance · machine-readable index on apis.io