Skip to main content
MX Technologies logo
  • Category: developer tools
  • Auth: BASIC
  • Composio-managed OAuth available? N/A
  • Tools: 36
  • Triggers: 0
  • Slug: MX_TECHNOLOGIES
  • Version: 20261101_00

Tools

Slug: 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

string
Optional timestamp in ISO 8601 format to record when the cancellation takes effect. Stored in metadata for auditability. Defaults to current time if not provided.
string
required
The MX user GUID to disable. Format: USR-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
string
Optional free-text reason for the cancellation. Stored in the user’s metadata field for auditability.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

object
required
Fields for creating a manual account. Only ‘name’ is required; all other fields are optional.
string
required
GUID of the user under which to create the account, must start with ‘USR-‘

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Audience API credential client ID (optional; falls back to env)
string
Audience API credential client secret (optional; falls back to env)

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

object
required
Member creation payload containing institution_code and credentials (for non-OAuth) or is_oauth flag (for OAuth flows).
string
required
The MX user GUID prefixed with ‘USR-’ (e.g., ‘USR-fa7537f3-48aa-a683-a02a-b18940482f54’). Obtain from List Users or Create User endpoints.
string
Base64-encoded payload to echo in member webhooks (max 1024 characters). Sent as X-CALLBACK-PAYLOAD header.
string
URL for OAuth redirect after authentication completes. Required for OAuth members.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Partner-defined unique identifier for the user. Use this to map between your system and MX. If not provided, MX will generate a GUID.
string
Email address for the user. Used for identification and communication.
string
Custom metadata as a JSON string. Store additional user info like creation date, name, or custom fields. Do not include sensitive information.
boolean
Set to true to create the user in a disabled state. Defaults to false.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
The unique user identifier. Use either the MX-defined user GUID (prefixed with ‘USR-’) or your partner-defined user ID.
string
required
The unique member identifier (prefixed with ‘MBR-’). Obtain this from the List Members endpoint.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

object
required
Widget configuration options. At minimum, must specify the widget ‘type’.
string
required
The unique MX user GUID. Must start with ‘USR-’ prefix (e.g., ‘USR-fa7537f3-48aa-a683-a02a-b18940482f54’).
object
Optional data aggregation request object for specifying products or additional data options.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_ACCOUNT_NUMBERS_BY_MEMBERTool to list account numbers for a specific member. Use after obtaining user and member GUIDs.

Input Parameters

integer
Page number of results (>=1).
string
required
MX user GUID (must start with ‘USR-’).
string
required
MX member GUID (must start with ‘MBR-’).
integer
Number of records per page (10-1000).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_ACCOUNT_OWNERSList 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.

Input Parameters

integer
Page number for paginated results (1-indexed). Defaults to 1 if not provided.
string
required
MX-defined unique user identifier. Must start with ‘USR-’ prefix.
string
required
MX-defined unique member identifier. Must start with ‘MBR-’ or ‘MEM-’ prefix.
integer
Number of records per page (10-1000). Defaults to 25 if not provided.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_ACCOUNTSTool to list all accounts for a user. Use after confirming the user GUID.

Input Parameters

integer
Page number of results to return (1-based).
array
Filter accounts by member use cases: ‘PFM’ and/or ‘MONEY_MOVEMENT’.
boolean
Only include accounts that were manually created.
string
required
MX user GUID (must start with ‘USR-’).
integer
Number of records per page (10-1000). Defaults to MX default of 25.
boolean
Only include accounts whose member is managed by the user.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for paginated results. Defaults to 1 if not specified.
string
required
The unique identifier (GUID) of the MX user. Obtain this from the List Users endpoint.
integer
Number of records per page (10-1000). Defaults to 25 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_CATEGORIESTool to list all categories for a user. Use when you need to fetch both default and custom categories for a given user GUID.

Input Parameters

integer
Page number of results to return. Must be >= 1.
string
required
The unique identifier (GUID) of the MX user.
integer
Number of records per page (10-1000). Defaults to 25.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_CHALLENGESTool to list MFA challenges for a member. Use when the member is in CHALLENGED state to retrieve prompts to answer.

Input Parameters

integer
Page number for paginated results, must be >= 1.
string
required
The unique identifier (GUID) for the MX user (prefix ‘USR-’).
string
required
The unique identifier (GUID) for the member.
integer
Number of records per page; valid range 10–1000 (default 25).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for pagination. Must be >= 1. Defaults to 1.
array
Filter institutions by ISO country codes. Supported values: ‘US’ (United States), ‘CA’ (Canada), ‘MX’ (Mexico).
integer
Number of records per page. Valid range: 10-1000. Defaults to 25.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_GOALSList 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.

Input Parameters

integer
Page number of results to return. Must be >= 1. Defaults to 1.
string
required
The unique identifier (GUID) of the MX user (e.g., ‘USR-…’).
integer
Number of records per page (10-1000). Defaults to 25.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_INSTITUTION_CREDENTIALSTool to list credential fields required by a given institution. Use after selecting the institution code; supports optional pagination.

Input Parameters

integer
Page number for pagination; must be >= 1.
string
required
MX-defined code for the institution (e.g., ‘mxbank’).
integer
Number of records per page for pagination; must be >= 1.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Filter to institutions whose name contains the given substring.
integer
Page number for pagination; must be >= 1.
array
Filter by ISO country codes (e.g., [‘US’, ‘CA’, ‘MX’]).
integer
Records per page; valid range: 10-1000. Defaults to 25; values >1000 reset to 25.
array
Filter by supported products; e.g., [‘account_verification’,‘identity_verification’,‘transactions’,‘history’,‘statements’,‘investments’].

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number of results to return (1-based).
string
required
MX user GUID (must start with ‘USR-’). Obtain from LIST_USERS action.
string
required
MX member GUID (must start with ‘MBR-’). Obtain from LIST_MEMBERS action.
integer
Number of records per page. Defaults to MX default if not specified.
boolean
Filter to accounts where the member is managed by the user (true) vs partner-managed (false). Omit to return all accounts.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for paginated results. Defaults to 1.
string ("PFM" | "MONEY_MOVEMENT")
Filter members by use case. ‘PFM’ for personal financial management, ‘MONEY_MOVEMENT’ for payment/transfer use cases.
string
required
The unique user identifier. Use either the MX-defined user GUID (prefixed with ‘USR-’) or your partner-defined user ID.
integer
Number of records per page. Valid range: 10-1000. Defaults to 25.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for paginated results. Starts at 1. Omit to get first page.
string
required
MX-assigned unique identifier for the user. Get this from the List Users action (format: USR-xxxxxxxx).
string
required
MX-assigned unique identifier for the member linked to a financial institution. Get this from the List Members action (format: MBR-xxxxxxxx).
integer
Number of records per page (1-100). Defaults to 25 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for pagination (1-indexed). Omit to get the first page.
string
required
The unique MX user identifier. Must start with ‘USR-’ prefix. Obtain from LIST_USERS action.
string
required
The unique MX member identifier. Must start with ‘MBR-’ prefix. Obtain from LIST_MEMBERS action for the user.
integer
Number of statements to return per page (10-1000). Defaults to 25 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for paginated results. Starts at 1. If not provided, defaults to the first page.
string
required
The unique MX user identifier (starts with ‘USR-’). Required to identify which user’s taggings to retrieve.
integer
Number of records to return per page (max 1000). If not provided, the API uses its default.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_TAGSList 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.

Input Parameters

integer
Page number of results to return (1-indexed). Defaults to 1 if not specified.
string
required
The unique identifier (GUID) of the MX user whose tags to list. Must start with ‘USR-’ prefix.
integer
Number of records per page (1-1000). Defaults to 25 if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

integer
Page number for pagination (1-based). Omit or set to 1 to get the first page.
integer
Filter to transactions on or before this date (at midnight). Unix timestamp in seconds. Default: 5 days in the future.
array
Request additional enhanced data with each transaction. Options: ‘repeating_transactions’ (recurring patterns), ‘merchants’ (merchant details), ‘classifications’ (transaction classifications), ‘geolocations’ (location data).
array
Filter by member use case. ‘PFM’ for personal finance management, ‘MONEY_MOVEMENT’ for payment initiation. Can specify one or both.
integer
Filter to transactions on or after this date. Unix timestamp in seconds. Default: 120 days ago.
string
required
The MX user GUID (starts with ‘USR-’) or the partner-defined user ID.
integer
Filter to transactions created in MX on or before this time. Unix timestamp in seconds.
integer
Filter to transactions last updated on or before this time. Unix timestamp in seconds.
integer
Filter to transactions created in MX on or after this time. Unix timestamp in seconds.
integer
Filter to transactions last updated on or after this time. Unix timestamp in seconds.
integer
Number of transactions to return per page. Range: 10-1000. Default: 25.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_LIST_TRANSACTIONS_BY_MEMBERTool to list transactions for a member. Use when you have valid user and member GUIDs and need their transactions.

Input Parameters

integer
Page number of results to return (1-based).
integer
Unix timestamp to filter transactions to this date (midnight); defaults to 5 days forward.
string
Comma-separated list of enhancements: repeating_transactions,merchants,classifications,geolocations
integer
Unix timestamp to filter transactions from this date; defaults to 120 days ago.
string
required
MX user GUID (must start with ‘USR-’).
string
required
MX member GUID (must start with ‘MBR-’ or ‘MEM-’).
integer
Unix timestamp to filter transactions to created time.
integer
Unix timestamp to filter transactions to created-at.
integer
Unix timestamp to filter transactions to updated-at.
integer
Unix timestamp to filter transactions from created time.
integer
Unix timestamp to filter transactions from created-at.
integer
Unix timestamp to filter transactions from updated-at.
integer
Number of records per page (10-1000). Defaults to MX default of 25.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Filter by partner-defined user ID.
integer
Page number for paginated results (>=1).
string
Filter by user email.
boolean
Filter to only disabled users.
integer
Number of records per page (10-1000).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_READ_ACCOUNTTool to retrieve details for a specific account. Use after obtaining valid user and account GUIDs to fetch up-to-date account information.

Input Parameters

string
required
The unique identifier (GUID) of the MX user.
string
required
The unique identifier (GUID) of the account.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_READ_CATEGORYTool to retrieve a default category by GUID. Use after confirming the default category GUID.

Input Parameters

string
required
The unique identifier (GUID) of the default category to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
required
The FDX account identifier to retrieve. For FDX endpoints, this is typically an opaque string like ‘acct-1234abcd’. For MX Platform fallback, use an MX account GUID starting with ‘ACC-’ or ‘ACT-’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_READ_INSTITUTIONTool 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.

Input Parameters

string
required
A unique identifier for each institution, defined by MX.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_READ_TRANSACTIONTool to retrieve details for a specific transaction by its GUID. Use when you need to fetch information about a particular transaction for a user.

Input Parameters

string
required
The unique identifier (GUID) of the MX user, starting with ‘USR-’.
string
required
The unique identifier (GUID) of the transaction, starting with ‘TRN-’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

string
Comma-separated list of optional enhancements: ‘repeating_transactions’ (identifies recurring patterns), ‘merchants’ (enriches with merchant name), ‘classifications’ (provides transaction type insights), ‘geolocations’ (provides geographic metadata). Example: ‘repeating_transactions,merchants,classifications,geolocations’
string
MX Platform API version (e.g., ‘v20250224’). This header is required for API calls.
string
required
Use either the user id you defined or the MX-defined user guid. See MX-Defined GUIDs vs IDs Defined by You.
string
required
Use either the member id you defined or the MX-defined member guid. See MX-Defined GUIDs vs IDs Defined by You.
string
required
Use either the account id you defined or the MX-defined account guid. See MX-Defined GUIDs vs IDs Defined by You.
string
required
Use either the transaction id you defined or the MX-defined transaction guid. See MX-Defined GUIDs vs IDs Defined by You.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_READ_TRANSACTION_RULETool 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.

Input Parameters

string
required
The unique identifier for a user, beginning with the prefix USR-.
string
required
The unique id for a transaction_rule, beginning with the prefix UTR-.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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

object
required
Transaction update payload containing the new description.
string
MX Platform API version (e.g., ‘v20250224’). This header is required for API calls.
string
required
Use either the user id you defined or the MX-defined user guid (e.g., ‘USR-0607e50a-e32d-40b3-b1d5-9452b791a064’).
string
required
Use either the member id you defined or the MX-defined member guid (e.g., ‘MBR-116c29e9-0cba-40c7-a8a7-279a488db92c’).
string
required
Use either the account id you defined or the MX-defined account guid (e.g., ‘ACT-c3ce40b9-f52f-4c7a-a572-d627f14edcf8’).
string
required
Use either the transaction id you defined or the MX-defined transaction guid (e.g., ‘TRN-dcf603d0-c31b-4609-8422-ebcb1689fd94’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: 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.

Input Parameters

string
required
The unique identifier (GUID) of the MX user. Must start with ‘USR-’ prefix.
object
required
Transaction rule object containing fields to update. At least one field must be provided.
string
required
The unique identifier (GUID) of the transaction rule to update. Must start with ‘UTR-’ prefix.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: MX_TECHNOLOGIES_UPDATE_USERS_TAGGINGSTool 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.

Input Parameters

object
required
Tagging object containing the new tag_guid to associate with the transaction.
string
required
The unique identifier for the user, must start with ‘USR-’ prefix.
string
required
The unique identifier for the tagging to update, must start with ‘TGN-’ prefix.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not