MX Technologies provides a comprehensive API platform for aggregating and enhancing financial data, enabling seamless connections to numerous financial institutions.
Creates a manual account for a specified MX user, for tracking an account that is not aggregated through MX. Manual accounts require manual updates rather than financial institution aggregation. The account may be created in the integration environment even when production is configured.
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.
Disable an MX user account by setting is_disabled to true. The update also replaces the user's metadata with a disabled timestamp and an optional cancellation reason.
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.
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 list account numbers for a specific member. Use after obtaining user and member GUIDs.
List account owners for a specific member using user and member GUIDs. Results are paginated and may include identity information such as names, addresses and contact details.
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.
List all financial goals for a specific MX user. Use this to retrieve a paginated list of the user's savings goals, including target amounts, progress, and completion dates. Requires a valid user GUID obtained from the LIST_USERS action.
Tool to list credential fields required by a given institution. Use after selecting the institution code; supports optional pagination.
Tool to list financial institutions supported by MX. Use when you need to retrieve available institutions with optional filters like name, country code, or products; supports pagination.
Tool to list accounts for a specific member. Use when you need to retrieve all accounts associated with a given user and member GUID.
List all members (financial institution connections) for a specific user. A member represents a connection between a user and a financial institution. Use this tool to retrieve all members linked to a user, including their connection status, aggregation state, and institution details. Useful for checking which accounts are connected, identifying connection issues, or finding member GUIDs for other operations. Returns paginated results with member details and pagination info.
Lists rewards and loyalty program data for a specific user and member, with pagination. A 404 response is returned as an empty rewards list, so an empty result does not necessarily mean no rewards exist.
Retrieve a paginated list of monthly account statements (PDF) for a specific member. Use this tool after obtaining valid user_guid (via LIST_USERS) and member_guid (via LIST_MEMBERS). Statements include bank/credit statements in PDF format. The uri field in each statement can be used to download the actual PDF.
List all taggings for a specific MX user. Taggings are links between custom tags and transactions - they show which labels have been applied to which transactions. Use this when you need to: - See all tag-transaction associations for a user - Find which transactions have been labeled with custom tags - Audit or review a user's transaction categorization Prerequisites: Obtain a valid user_guid from LIST_USERS first.
List all custom tags associated with a specific MX user. Tags are labels that can be applied to transactions for organization. Every user has a default 'Business' tag. Returns paginated results. Use this to retrieve tag GUIDs needed for tagging transactions.
Retrieve all financial transactions for an MX user across all their connected accounts and members. Use this tool to get a user's complete transaction history. Supports pagination, date filtering, and optional enhanced data (merchants, geolocations, classifications, repeating transactions). Prerequisites: You need a valid MX user GUID (starts with 'USR-'). Get this from the List Users action.
Tool to list transactions for a member. Use when you have valid user and member GUIDs and need their transactions.
List all users in the MX Platform. Use this to retrieve a paginated list of user accounts with optional filters by ID, email, or disabled status. Each user represents an end user accessing MX Platform through your application. Returns user details including guid (MX identifier), id (partner-defined identifier), email, and account status flags.
Tool to retrieve details for a specific account. Use after obtaining valid user and account GUIDs to fetch up-to-date account information.
Tool to retrieve a default category by GUID. Use after confirming the default category GUID.
Retrieve details for a specific account using its FDX identifier, including balances, status, and account attributes when available. FDX access requires an MX Data Access OAuth bearer token; MX Platform Basic credentials are not used for FDX requests. MX Platform account GUIDs can also be used, with account discovery limited to the first page of users and the first page of each user's accounts.
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 retrieve details for a specific transaction rule by its GUID. Use when you need to fetch information about a particular transaction rule for a user.
Tool to retrieve Audience API credentials. Use when obtaining client_id and client_secret for Audience Service authentication before generating an access token. Credentials must be created in the Partner Dashboard (Partner Administrator → Authentication → Audience API Key). The tool prefers explicitly provided values, then falls back to environment variables.
Tool to update a specific transaction's description. Use when you need to modify the description of an existing transaction.
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.
The MX Technologies integration connects your Dench AI CRM directly to MX Technologies, so agents can read and act on your MX Technologies data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
36 actions are available for agents to invoke on your behalf. Every call runs through MX Technologies's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find MX Technologies and click Connect — you'll authorize access through MX Technologies's own sign-in flow. No API keys or code required.
Ask an agent to use MX Technologies in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench MX Technologies integration connects your AI CRM to MX Technologies, so AI agents can work with your MX Technologies data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The MX Technologies integration currently exposes 36 actions, including Create account, Create member, Create Partner Account, Disable MX User Account, Fetch rewards, and Get configurable widget URL. Agents invoke them on your behalf from chat or from automations.
No. You connect MX Technologies from your Dench workspace using MX Technologies's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through MX Technologies's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the MX Technologies connection from your workspace settings at any time.