directory
The same rows /v1/institutions/search returns and the same list Link searches — grouped by type and country, with the routing chain and product support spelled out on each institution's page.
What being listed here does and does not mean
FeelConnect does not hold bank connections of its own. Every institution in the catalog carries an ordered chain of connectors, and live traffic goes to the first one whose credentials are present in the deployment you are calling.
Some connectors an operator can switch on alone in minutes — GoCardless Bank Account Data (UK and EU banks, free self-signup under their PSD2 licence), Coinbase, Kraken, PayPal, public-address crypto wallets, and CSV / OFX / QFX import. Others need a signed business relationship before they will serve production data, including Plaid, MX, Finicity, Akoya, and Stripe Financial Connections. Where an institution has no enabled connector, a live call returns provider_error rather than pretending.
The sandbox is the exception and it is always on: test keys resolve to the simulated network regardless of credentials, so the full integration is buildable on day one. See going live for the provider-by-provider breakdown.
browse
Every entry links to a page with that institution's connector chain, product support, and a Link snippet you can paste.
938 institutions
Retail and commercial banks. Checking, savings, card, and loan accounts with transaction history.
Member-owned institutions. Share draft, share savings, and loan accounts, routed like any other bank.
Brokerages and retirement providers. Positions, securities, and trade history alongside cash balances.
Balance-and-transfer accounts held at a payment provider rather than a bank.
Custodial exchange accounts: asset balances, holdings, and ledger activity.
Self-custody wallets tracked by public address. Read-only by construction — no key ever leaves the user.
Commerce, payroll, and accounting platforms that hold a balance or a transaction ledger.
in code
The directory is a view of the institution table; the API is the interface you build against.
POST /v1/institutions/search takes a query plus optional types and country_codes, matches on name and search terms, orders by the popularity that also ranks Link’s results, and returns at most twenty institutions. POST /v1/institutions/get_by_id returns exactly one. Both are documented in the institutions reference, and the API explorer runs them against the sandbox from the browser.
faq
keep reading