MX Technologies

Tool to retrieve details for a specific institution by code. Use when you need to get information about a particular financial institution using its unique code.

Tool to retrieve details for a specific transaction by its GUID. Use when you need to fetch information about a particular transaction for a user.

Tool to retrieve details for a specific transaction by account. Use when you need to fetch information about a particular transaction using user, member, account, and transaction identifiers. Supports optional enhancements like merchant details, geolocations, classifications, and repeating transaction patterns.

Tool to list account numbers for a specific member. Use after obtaining user and member GUIDs.

Tool to list account owners for a specific member. Returns identity information (name, address, contact details) for all account owners associated with the member's accounts. Requires user_guid and member_guid. Use this to retrieve account holder identity data for verification or compliance purposes.

Tool to list all accounts for a user. Use after confirming the user GUID.

List all budgets for a specific MX user. Budgets track spending limits for categories. Prerequisites: Obtain a valid user_guid from the List Users endpoint first. Note: Budgets are automatically generated based on transaction history or can be manually created. If a user has no budgets, an empty list is returned.

Tool to list all categories for a user. Use when you need to fetch both default and custom categories for a given user GUID.

Tool to list MFA challenges for a member. Use when the member is in CHALLENGED state to retrieve prompts to answer.

List the partner's favorite financial institutions, sorted by popularity. Use this tool to retrieve institutions that have been pre-configured as favorites for the partner account. Results are paginated and can be filtered by country. Note: Favorite institutions must be configured by MX - contact MX support to set up favorites.

Creates a manual account for a specified user in MX Platform. Use this tool when you need to: - Add an external/off-platform account that isn't aggregated through MX - Create a test account for development purposes - Track accounts from institutions not supported by MX aggregation Note: Manual accounts do not aggregate data from financial institutions. They are created under the special 'Manual Institution' member and require manual updates for balance and transaction information. Requires: A valid user_guid (obtained from List Users or Create User).

Create a member to connect a user to a financial institution. A member represents the relationship between an MX user and a financial institution. For non-OAuth institutions, provide credentials obtained from List Institution Credentials. For OAuth institutions, set is_oauth=true and use the returned oauth_window_uri. Prerequisites: - user_guid from List Users or Create User - institution_code from List Institutions - credentials from List Institution Credentials (for non-OAuth) Test credentials for MX Bank (mxbank): username='mxuser', password='password'

Create a new user (partner account) in the MX Platform. Users represent end-users in your application and are required before creating members, accounts, or accessing financial data. Use this tool to provision a new user record in MX.

Retrieve a configurable widget URL for embedding MX widgets (Connect, Transactions, Pulse, etc.). Use this tool to generate a single-use URL for displaying MX widgets to end users. The URL expires after 10 minutes or immediately upon first use, so always request a fresh URL when loading the widget. Requires a valid user_guid (obtained from list_users or create_user actions).

Tool to update a specific transaction's description. Use when you need to modify the description of an existing transaction.

Initiate rewards aggregation for a specific member. This triggers an async job to gather rewards data (points, miles, etc.) from the member's financial institution. Use List Rewards to retrieve the results after aggregation completes.

Tool to update an existing transaction rule. Use when you need to modify how transactions are categorized or described based on pattern matching. Note: Changes to match_description will only be applied to future transactions.

Tool to update a tagging for an MX user. Use when you need to change which tag is associated with a specific transaction. A tagging represents the link between a custom tag and a transaction.

Disables an MX user account, preventing background updates to accounts and transactions and restricting data access. The user can be re-enabled later via the update user endpoint. Uses MX Platform API: PUT /users/{user_guid} with is_disabled=true.