Skip to content

NEWUnify Agents (MCP): governed AI access to finance data. Early access.See Unify Agents

TL

BANK DATA INTEGRATION

Teller integration with the Unify Bank Feeds API

Planned: Teller bank accounts, transactions and balances on one data model.

RoadmapCredentials · Sandbox yes

GET /v1/finance/bank-accounts?platform=teller&limit=1

API design preview

Request

curl "https://api.unifyint.com/v1/finance/bank-accounts?platform=teller&limit=1" \
  -H "Authorization: Bearer $UNIFY_API_KEY"

200 OK · API design preview

{
  "data": [
    {
      "id": "ban_01EXAMPLE",
      "object": "bank_account",
      "remote_id": "example-1001",
      "name": "Accounts Receivable",
      "type": "asset",
      "currency": "USD",
      "updated_at": "2026-10-28T14:02:11Z",
      "raw": { "...": "original Teller record, unchanged" }
    }
  ],
  "next_cursor": null
}

API design preview. Field names may change before general availability.

On our roadmap. Request it to move it up.

Request Teller

About the Teller integration

Teller connects apps directly to US bank accounts through its own bank integrations rather than screen scraping. Unify Int reads Teller accounts, balances and transactions into one bank data model.

Teller authenticates API clients with mutual TLS certificates and uses Teller Connect for end-user enrollment, returning an access token per enrollment and sending webhooks for enrollment events. Unify Int maps accounts, balances and transactions to the Unify Graph.

Status
Roadmap
Category
Bank data
Auth
Credentials
Sandbox
Available
Webhooks
Yes
Bank feeds
Supported
Regions
US

Supported objects

Read and write status for each Teller object in the Unify Bank Feeds API. Write appears only where write-back is confirmed.

  • Bank Accounts

    Read on roadmap
  • Transactions

    Read on roadmap
  • Balances

    Read on roadmap

Why build Teller on Unify Int

  • One data model

    Teller records arrive in the same Unify Graph shape as every other platform in the category, with the original record kept in raw.

  • Unify Connect

    A white-label flow for your customers to authorize Teller. Tokens are stored and refreshed for you.

  • Custom fields and passthrough

    Map Teller custom fields per connection, and call any endpoint the model does not cover through passthrough requests.

  • Unify Monitor

    Request logs, sync health and alerts for every Teller connection, so support can see what happened.

Teller integration questions

Does Unify Int support Teller bank accounts and transactions?
Teller is on the Unify Int roadmap. The planned scope covers reading bank accounts, transactions and balances. Request it to move it up, or ask the Technology Center about a custom build.
How do customers connect their Teller account?
Your customer enrolls their bank through Teller Connect inside Unify Connect; API calls use your Teller certificate and the enrollment's access token.
Is there a Teller sandbox for testing?
Yes. Teller offers sandbox and development environments with test credentials.
How often does Teller data sync?
Unify Sync uses Teller webhooks for change detection, so new and updated records usually arrive within minutes, with scheduled polling as a safety net. You can set the schedule per object.
Can I access Teller custom fields?
Teller transaction details (counterparty, category) are kept on each record; the full record stays in `raw`.

Get started

Connect once. Build everything else on top.

Request sandbox access, or book 30 minutes with an engineer to map your integrations.

Free sandbox access. No credit card. Reply within one business day.