Skip to content

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

M

BANK DATA INTEGRATION

MX integration with the Unify Bank Feeds API

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

RoadmapAPI key · Sandbox yes

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

API design preview

Request

curl "https://api.unifyint.com/v1/finance/bank-accounts?platform=mx&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 MX 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 MX

About the MX integration

MX is a financial data platform that aggregates and enhances bank account data for banks, credit unions and fintechs. Unify Int reads MX accounts, balances and transactions into one bank data model.

The MX Platform API uses a client ID and API key, with the MX Connect widget for member consent and webhooks for aggregation events. Unify Int maps members' accounts, balances and transactions, including MX's cleansed descriptions and categories, to the Unify Graph.

Status
Roadmap
Category
Bank data
Auth
API key
Sandbox
Available
Webhooks
Yes
Bank feeds
Supported
Regions
US, CA

Supported objects

Read and write status for each MX 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 MX on Unify Int

  • One data model

    MX 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 MX. Tokens are stored and refreshed for you.

  • Custom fields and passthrough

    Map MX 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 MX connection, so support can see what happened.

MX integration questions

Does Unify Int support MX bank accounts and transactions?
MX 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 MX account?
Your customer connects their institution through the MX Connect widget inside Unify Connect, using your MX client credentials.
Is there a MX sandbox for testing?
Yes. MX provides an integration environment with test institutions.
How often does MX data sync?
Unify Sync uses MX 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 MX custom fields?
MX enhanced fields (cleansed description, category, merchant) are kept on each transaction; 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.