APIs and connectivity: public portal comparison

This page compares major banks using what is publicly visible in developer portals and official product/implementation pages. It focuses on discoverability, onboarding visibility, documentation clarity, and public limitations (what is not visible publicly). It now includes a requested 10-bank API cohort for J.P. Morgan, Citi, HSBC, Bank of America, Barclays, Goldman Sachs, BNP Paribas, UBS, RBC, and TD.

Developer portals Public limitations API + host-to-host Citi vs JPM 10-bank API cohort
Last verified: April 6, 2026
Confidence: Medium (portal content can change; private onboarding can add scope)
Legal/compliance review: Recommended before publication

Citi vs JPMorgan: API visibility comparison

A careful, factual view based on public disclosures and public portal documentation.

Citi sources: CitiConnect® API portal announcement (Apr 12, 2021) · Citi Implementations (undated)
JPM sources: J.P. Morgan llms.txt (undated) · Become a client (undated)
Last verified: April 6, 2026

Publicly visible API considerations and limitations

Neutral, factual guidance focused on what is visible publicly and what typically must be confirmed during onboarding.

Public portals are not complete inventories

Developer portals typically show a curated subset of capabilities. Full scope can depend on client segment, geography, and entitlements.

Label: Analyst interpretation (common market pattern)
Confidence: High

Region and eligibility differences are common

APIs and connectivity options can differ by country, entity, currency, and product. Treat public pages as starting points, not definitive eligibility statements.

Label: Analyst interpretation
Related: NAM, U.S., Canada

Implementation steps often move into engagement

Some banks publish onboarding steps publicly; others reference implementations teams and testing portals. Even with public steps, certification and operating model readiness are usually engagement-led.

Label: Sourced summary + analyst interpretation
Confidence: Medium

Commercial terms are usually not public

Pricing, SLAs, and eligibility terms are typically handled through relationship and contracting. Avoid publishing claims about latency/uptime unless officially disclosed.

Label: Analyst guidance (legal-risk-aware)
Related: Legal page

Client operating model matters

APIs change ownership boundaries: entitlement admin, exception handling, reconciliation mapping, and control models. Use a client-side checklist before kickoff.

Hybrid connectivity is normal

APIs often coexist with host-to-host and files (especially for high volume). Design for both: initiation, status, and reconciliation flows.

Public API category map and entitlement paths

Requested API comparison cohort: J.P. Morgan, Citi, HSBC, Bank of America, Barclays, Goldman Sachs, BNP Paribas, UBS, RBC, and TD.

Authorized-access rule: financeAI.tech does not attempt to bypass gated portals. If a bank does not publish a numeric technical constraint publicly, the limitation is recorded as Not disclosed in public portal; requires entitlement.

How to read this matrix

The first table maps which API families are visible publicly and how a treasury team legitimately gets access. The second table gives one representative API limitation per bank, with hard limits only where the bank publishes them.

Public API limitations database

Representative treasury-relevant API rows only. Hard limits are shown only when the bank publishes them in public documentation.

Peer portals and official links (starting points)

A short list of major bank developer portals for cross-checking. Portal visibility varies and can change.