FeelConnect▍
ProductsDocsPricingChangelog
Sign inGet API keys

Search documentation

Fuzzy search across every docs page and section

Getting started/Overview

Getting started

  • Overview
  • Quickstart
  • Authentication
  • Environments and sandbox
  • Link
  • Going live

API reference

  • Link tokens
  • Institutions
  • Items
  • Accounts
  • Transactions
  • Identity
  • Income
  • Assets
  • Investments
  • Liabilities
  • Recurring
  • Categories
  • AI products

Platform

  • Webhooks
  • Errors
  • Rate limits and quotas
  • SDKs
  • GraphQL
  • MCP and AI agents
  • Changelog
  1. Docs
  2. Getting started
  3. Overview
NextQuickstart

On this page

  • What you can build on
  • How a connection works
  • Connector network
  • Where to start
FeelConnect▍

The developer-first financial data platform.

All systems operational

Products

Universal LinkData APIsAI enrichmentPricing

Developers

DocumentationAPI explorerDashboardGet API keys

Company

HomeChangelogfeels.moneySign in

Legal

PrivacyTermsSecurityData processing
© 2026 FeelConnect. All rights reserved./v1 · FC-Version 2026-07-01

Getting started

Overview

FeelConnect is the developer-first financial data platform: one Link flow, one /v1 API for accounts, transactions, investments, liabilities, and AI enrichment.

FeelConnect is a financial data platform. Your users connect their bank, payment-app, investment, and crypto accounts through a single Link flow; you read normalized data and AI enrichment through a single /v1 API.

Every endpoint is POST with a JSON body and secret-key bearer auth. Data shapes are stable, typed, and identical across the 11 official SDKs.

What you can build on

  • Link — an embeddable modal that handles institution search, OAuth, credentials, MFA, account selection, and consent. See Link.
  • Core data products — accounts, balances, transactions (cursor sync), identity, income, assets, investments, liabilities, recurring streams. See the API reference.
  • AI products — nine enrichment endpoints (categorization, subscription detection, cash-flow forecasting, health score, fraud signals, and more) that work with an access_token or a raw payload. See AI products.
  • Webhooks — signed event deliveries with automatic retries. See Webhooks.
  • GraphQL — an optional read gateway over the same data. See GraphQL.
  • MCP — a Model Context Protocol server so AI agents can call FeelConnect as tools. See MCP and AI agents.

How a connection works

The flow is three server calls and one frontend embed. Your server never sees user credentials; Link returns a short-lived public_token that you exchange for a persistent access_token.

curl
# 1. server: create a link_token
curl https://api.feelconnect.dev/v1/link/token/create \
-H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{"user":{"client_user_id":"user-123"},"products":["transactions","balances"]}'
# 2. frontend: FeelConnect.open({ linkToken, onSuccess }) -> public_token
# 3. server: exchange for an access_token
curl https://api.feelconnect.dev/v1/link/token/exchange \
-H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{"public_token":"<from Link onSuccess>"}'
# 4. server: read data forever after
curl https://api.feelconnect.dev/v1/transactions/sync \
-H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{"access_token":"fc_at_..."}'

Connector network

FeelConnect routes each institution to the best available connector: a fully simulated sandbox network (always on), manual CSV/OFX/QFX import, evm-wallet public-address crypto tracking, and upstream aggregators (Plaid, MX, Finicity, Akoya, GoCardless, Stripe Financial Connections, Coinbase, Kraken, PayPal, Wise) that activate per deployment. The connector is an implementation detail — the API shape never changes.

Sandbox is always fully functional

Test keys (fc_sk_test_…) always resolve to the sandbox network: 76 institutions, deterministic 24-month data, OAuth and MFA simulation. You can build and demo the entire integration without any live agreements. See Environments and sandbox.

Where to start

  • Quickstart — keys to synced transactions in about ten minutes.
  • Authentication — how keys, environments, and request IDs work.
  • API explorer — run real sandbox calls from the browser.
  • Errors and rate limits — what to handle in production.