APIs and connectivity: public portal comparison

This page shows what a buyer can verify before entitlement: which banks publish treasury APIs publicly, how easy those APIs are to discover, where onboarding and sandbox paths are visible, and where important limits still sit behind relationship-led onboarding. It covers a requested 10-bank cohort: 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 16, 2026
Confidence: Medium (portal content can change; private onboarding can add scope)
Legal/compliance review: Recommended before publication

Citi vs JPMorgan: API visibility comparison

Use this table to see which bank is easier to understand in public before a client team enters onboarding.

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 16, 2026

Publicly visible API considerations and limitations

These are the practical boundaries a product, sales, or implementation team should keep in mind when reading public portals.

Public portals are not complete inventories

Public portals usually show enough to frame a deal, not always enough to design the full solution. Final scope still depends on client segment, geography, and entitlements.

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

Region and eligibility differences are common

Country, entity, currency, and product rules often change the answer. Treat public pages as a starting point until the bank confirms the client setup.

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

Implementation steps often move into engagement

The first part of onboarding may be public. The detailed work on certification, credentials, operating model, and readiness usually moves into implementations and relationship channels.

Label: Sourced summary + analyst interpretation
Confidence: Medium

Commercial terms are usually not public

Pricing, SLAs, and eligibility almost always sit outside the public portal. Avoid performance claims unless the bank has disclosed them officially.

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

Client operating model matters

The main delivery risk is often internal readiness, not the API itself. Entitlements, exception handling, reconciliation, and controls should be clarified before kickoff.

Hybrid connectivity is normal

Most large programs end up hybrid: APIs for real-time actions, files or host-to-host for scale and control, and portals for approvals or exceptions.

Public API category map and entitlement paths

This is the fast map of who publishes what, how access is granted, and where public evidence stops.

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 shows which API families are visible publicly and the legitimate path to access them. The second table shows one representative public constraint per bank, with hard limits only where the bank publishes them.

Public API limitations database

Treasury-relevant examples only. Hard limits appear only where the bank publishes them in public documentation.

Peer portals and official links (starting points)

Use these as source-check starting points, not as complete product inventories.