- Category: developer tools
- Auth: BASIC
- Composio-managed OAuth available? N/A
- Tools: 36
- Triggers: 0
- Slug:
MX_TECHNOLOGIES - Version: 20261101_00
Tools
Disable MX User Account
Disable MX User Account
MX_TECHNOLOGIES_CANCEL_PARTNER_ACCOUNTDisable 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.Input Parameters
Output
Create account
Create account
MX_TECHNOLOGIES_CREATE_ACCOUNTCreates 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.Input Parameters
Output
Retrieve Audience API Credentials
Retrieve Audience API Credentials
MX_TECHNOLOGIES_CREATE_AUDIENCE_API_CREDENTIALSTool 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.Input Parameters
Output
Create member
Create member
MX_TECHNOLOGIES_CREATE_MEMBERCreate 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’Input Parameters
Output
Create Partner Account
Create Partner Account
MX_TECHNOLOGIES_CREATE_PARTNER_ACCOUNTCreate 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.Input Parameters
Output
Fetch rewards
Fetch rewards
MX_TECHNOLOGIES_FETCH_REWARDSInitiate 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.Input Parameters
Output
Get configurable widget URL
Get configurable widget URL
MX_TECHNOLOGIES_GET_CONFIGURABLE_WIDGET_URLRetrieve 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).Input Parameters
Output
List Account Numbers by Member
List Account Numbers by Member
List account owners
List account owners
List accounts
List accounts
List budgets
List budgets
MX_TECHNOLOGIES_LIST_BUDGETSList 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.Input Parameters
Output
List categories
List categories
List challenges
List challenges
List favorite institutions
List favorite institutions
MX_TECHNOLOGIES_LIST_FAVORITE_INSTITUTIONSList 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.Input Parameters
Output
List goals
List goals
List institution credentials
List institution credentials
List institutions
List institutions
MX_TECHNOLOGIES_LIST_INSTITUTIONSTool 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.Input Parameters
Output
List member accounts
List member accounts
MX_TECHNOLOGIES_LIST_MEMBER_ACCOUNTSTool to list accounts for a specific member. Use when you need to retrieve all accounts associated with a given user and member GUID.Input Parameters
Output
List members
List members
MX_TECHNOLOGIES_LIST_MEMBERSList 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.Input Parameters
Output
List rewards
List rewards
MX_TECHNOLOGIES_LIST_REWARDSLists 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.Input Parameters
Output
List statements by member
List statements by member
MX_TECHNOLOGIES_LIST_STATEMENTS_BY_MEMBERRetrieve 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.Input Parameters
Output
List taggings
List taggings
MX_TECHNOLOGIES_LIST_TAGGINGSList 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.Input Parameters
Output
List transactions
List transactions
MX_TECHNOLOGIES_LIST_TRANSACTIONSRetrieve 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.Input Parameters
Output
List transactions by member
List transactions by member
List users
List users
MX_TECHNOLOGIES_LIST_USERSList 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.Input Parameters
Output
Read account
Read account
Read category
Read category
Read FDX account
Read FDX account
MX_TECHNOLOGIES_READ_FDX_ACCOUNTRetrieve 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.Input Parameters
Output
Read institution
Read institution
Read transaction
Read transaction
Read transaction by account
Read transaction by account
MX_TECHNOLOGIES_READ_TRANSACTION_BY_ACCOUNTTool 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.Input Parameters
id you defined or the MX-defined user guid. See MX-Defined GUIDs vs IDs Defined by You.id you defined or the MX-defined member guid. See MX-Defined GUIDs vs IDs Defined by You.id you defined or the MX-defined account guid. See MX-Defined GUIDs vs IDs Defined by You.id you defined or the MX-defined transaction guid. See MX-Defined GUIDs vs IDs Defined by You.Output
Read transaction rule
Read transaction rule
Update transaction
Update transaction
MX_TECHNOLOGIES_UPDATE_TRANSACTIONTool to update a specific transaction’s description. Use when you need to modify the description of an existing transaction.Input Parameters
id you defined or the MX-defined user guid (e.g., ‘USR-0607e50a-e32d-40b3-b1d5-9452b791a064’).id you defined or the MX-defined member guid (e.g., ‘MBR-116c29e9-0cba-40c7-a8a7-279a488db92c’).id you defined or the MX-defined account guid (e.g., ‘ACT-c3ce40b9-f52f-4c7a-a572-d627f14edcf8’).id you defined or the MX-defined transaction guid (e.g., ‘TRN-dcf603d0-c31b-4609-8422-ebcb1689fd94’).Output
Update transaction rules
Update transaction rules
MX_TECHNOLOGIES_UPDATE_TRANSACTION_RULESTool 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.