Environments and sandbox

FeelConnect has two data planes. Test is a complete simulation — institutions, auth flows, and 24 months of realistic data — available on every plan. Live talks to real connectors and requires the Startup plan or above.

Test credentials

Inside Link, any sandbox institution accepts these credentials:

Deterministic data engine

Every sandbox item is seeded by its item_id, so the data is random-looking but stable across calls — ideal for tests and demos. Each item gets:

• 24 months of transactions: biweekly payroll, rent or mortgage, subscriptions, groceries, dining, transport, and occasional travel bursts drawn from a ~90-merchant pool.
• Balances consistent with those flows, plus a credit card with a limit and APR.
• Investment holdings across 12 tickers with a deterministic price walk.
• Liabilities (card APR, student loan, mortgage), identity records, and income streams.
• Date-anchored generation — new transactions keep arriving as real time passes, so /transactions/sync always has something new eventually.

Sandbox helpers

Two endpoints exist only in the test environment to script hard-to-reach states:

Fires any webhook event type at your registered endpoints for the item.

curl https://api.feelconnect.dev/v1/sandbox/fire_webhook \
  -H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"access_token":"fc_at_…","type":"transactions.sync_updates_available"}'

{
  "fired": true
}

Forces the item into login_required, emitting an item.error webhook — exactly what happens when a real institution invalidates credentials. Use it to test update mode.

curl https://api.feelconnect.dev/v1/sandbox/item/reset_login \
  -H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"access_token":"fc_at_…"}'

{
  "reset": true
}