MX

Bring one MX user's bank transactions into DataOS

This guide brings one MX user's bank transactions (the transactions MX has collected for that user's linked accounts) into DataOS.

mx.com
REST API
Financial services & market data

What you need

An MX client ID and API key, plus the ID of the user to read

Who can get it

Your MX account contact or administrator

Where data lands

A governed table in your DataOS lakehouse

Connection type

REST API

How the connection works

Source
MX
DataOS connector
Keeps it up to date
DataOS lakehouse
Governed data product

The connector uses your MX keys to read the user's transactions, going back over the last day again to catch changes, and refreshes the table in DataOS. It only reads.

What's next

Ready to bring this data into DataOS?

See it in a demo

Watch the data land in DataOS as a governed data product. Book a demo

Read the DataOS docs

How connectors, data products and governance fit together. dataos.info

Connect another source