MX offers a full public REST API with a self-serve developer portal and sandbox. The current Platform API runs alongside the legacy Atrium API. Auth is HTTP Basic with client_id and api_key, calls must originate from whitelisted IPs, and webhooks cover aggregation and connection events.
MX scores B on the API Report Card. MX offers a full public REST API with a self-serve developer portal and sandbox. The current Platform API runs alongside the legacy Atrium API. Auth is HTTP Basic with client_id and api_key, calls must originate from whitelisted IPs, and webhooks cover aggregation and connection events.
MX has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
MX (MX Technologies, Inc., originally founded as MoneyDesktop in 2010 by Ryan Caldwell in Lehi, Utah) is a financial data platform that combines bank/credit-union account aggregation, data enhancement (cleansing, categorization, enrichment), and embedded money-experience widgets for financial institutions and fintechs.
Vertical: Financial Services (open banking / data aggregation / data enhancement / embedded money-experience infrastructure). Account aggregation from 13,000+ US/Canadian financial institutions (screen-scrape + OAuth + FDX where supported). Instant Account Verification (IAV) for ACH origination, account funding, and payout setup.
Very high within US financial services infrastructure. MX is consistently named as one of the top-four US financial data aggregators alongside Plaid, Finicity (Mastercard Open Banking), and Envestnet Yodlee.
End-user (consumer / SMB) consumer-permissioned FI credentials and OAuth tokens (held by MX, abstracted from the API caller). Connected accounts: account numbers (masked), routing numbers (verified), account type, currency, owner name and address.
MX was founded in 2010 as MoneyDesktop, rebranded to MX Technologies, and is approximately 15-16 years old as of 2026. Reached unicorn status in January 2021 with a ~$1.9B valuation after a $300M raise led by TPG.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.