Bank of America
Bank of America is a multinational investment bank and financial services holding company providing consumer banking, wealth management, corporate banking, and investment banking services worldwide. The CashPro Developer Studio provides REST APIs for corporate treasury clients to automate account management, payments, balance reporting, and statement access, supporting over 350 payment types and integration with TMS and ERP platforms.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Bank of America the way a machine reads it — 80 machine-readable artifacts across 6 APIs, 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 — Bank of America scores 58.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Bank of America
Each block below is one kind of artifact we hold for Bank of America. 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 6
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.
Bank of America Accounts API
The Accounts API from Bank of America — 2 operation(s) for accounts.
Bank of America Balances API
The Balances API from Bank of America — 1 operation(s) for balances.
Bank of America Banking API
Banking operations
Bank of America Payments API
The Payments API from Bank of America — 2 operation(s) for payments.
Bank of America Statements API
The Statements API from Bank of America — 2 operation(s) for statements.
Bank of America Transactions API
The Transactions API from Bank of America — 1 operation(s) for transactions.
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Bank of America API
OPEN COLLECTIONBank of America CashPro API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Bank of America GraphQL Schema
This conceptual GraphQL schema models the Bank of America CashPro API platform and broader retail banking services. It covers the full surface area of consumer and corporate ban...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bank Of America Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bank Of America Finops
FINOPSFeatures 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Account Management
Programmatic access to CashPro account details and metadata.
Balance Reporting
Real-time ledger, available, and collected balance queries.
Transaction History
Paginated transaction history with date range filtering.
Payment Initiation
Initiate payments across 350+ payment types including ACH, wire, SWIFT, and RTP.
Payment Status Tracking
Real-time payment status monitoring and cancellation support.
Statement Access
Programmatic retrieval of monthly account statements.
OAuth2 Security
Client credentials OAuth2 flow for secure API access.
TMS/ERP Integration
Pre-built connectors for 28+ Treasury Management and ERP platforms.
Sandbox Environment
Developer sandbox for testing and accelerated onboarding.
Scroll within the panel for all 9 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Bank Of America Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Bank of America API Rules
SPECTRALBank of America API Rules
SPECTRALJSON Schema 13
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Account
JSON SCHEMAAccountListResponse
JSON SCHEMABalance
JSON SCHEMABalanceResponse
JSON SCHEMABeneficiary
JSON SCHEMAErrorResponse
JSON SCHEMAPaymentListResponse
JSON SCHEMAPaymentRequest
JSON SCHEMAPaymentResponse
JSON SCHEMAStatement
JSON SCHEMAStatementListResponse
JSON SCHEMATransaction
JSON SCHEMATransactionListResponse
JSON SCHEMAScroll within the panel for all 13 ·
JSON Structure 13
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Account Structure
JSON STRUCTUREAccountlistresponse Structure
JSON STRUCTUREBalance Structure
JSON STRUCTUREBalanceresponse Structure
JSON STRUCTUREBeneficiary Structure
JSON STRUCTUREErrorresponse Structure
JSON STRUCTUREPaymentlistresponse Structure
JSON STRUCTUREPaymentrequest Structure
JSON STRUCTUREPaymentresponse Structure
JSON STRUCTUREStatement Structure
JSON STRUCTUREStatementlistresponse Structure
JSON STRUCTURETransaction Structure
JSON STRUCTURETransactionlistresponse Structure
JSON STRUCTUREScroll within the panel for all 13 ·
Examples 13
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Account Example
EXAMPLEAccountlistresponse Example
EXAMPLEBalance Example
EXAMPLEBalanceresponse Example
EXAMPLEBeneficiary Example
EXAMPLEErrorresponse Example
EXAMPLEPaymentlistresponse Example
EXAMPLEPaymentrequest Example
EXAMPLEPaymentresponse Example
EXAMPLEStatement Example
EXAMPLETransaction Example
EXAMPLEScroll within the panel for all 13 ·
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Treasury Automation
Automate daily cash positioning, balance reporting, and payment workflows.
ERP Integration
Connect SAP, Oracle, or other ERP systems to Bank of America CashPro.
Payments Hub
Centralize payment initiation across ACH, wire, SWIFT, and real-time payment rails.
Liquidity Management
Real-time visibility into global account balances for liquidity decisions.
Reconciliation
Automated transaction download for account reconciliation workflows.
Cash Concentration
Sweep and concentration account management via API.
Integrations 7
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SAP
Oracle
Kyriba
Sage Intacct
Microsoft Dynamics
Coupa
Workday
Scroll within the panel for all 7 ·
Resources
Every other property we hold for Bank of America — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bank-of-america · machine-readable index on apis.io