# MX Technologies

MX Technologies provides a comprehensive API platform for aggregating and enhancing financial data, enabling seamless connections to numerous financial institutions.

- **Category:** developer tools
- **Auth:** BASIC
- **Composio Managed App Available?** N/A
- **Tools:** 36
- **Triggers:** 0
- **Slug:** `MX_TECHNOLOGIES`
- **Version:** 20260312_00

## Tools

### Disable MX User Account

**Slug:** `MX_TECHNOLOGIES_CANCEL_PARTNER_ACCOUNT`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `effective_date` | string | No | 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. |
| `encoded_account_id` | string | Yes | The MX user GUID to disable. Format: USR-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |
| `cancellation_reason` | string | No | Optional free-text reason for the cancellation. Stored in the user's metadata field for auditability. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create account

**Slug:** `MX_TECHNOLOGIES_CREATE_ACCOUNT`

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).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `account` | object | Yes | Fields for creating a manual account. Only 'name' is required; all other fields are optional. |
| `user_guid` | string | Yes | GUID of the user under which to create the account, must start with 'USR-' |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Retrieve Audience API Credentials

**Slug:** `MX_TECHNOLOGIES_CREATE_AUDIENCE_API_CREDENTIALS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `client_id` | string | No | Audience API credential client ID (optional; falls back to env) |
| `client_secret` | string | No | Audience API credential client secret (optional; falls back to env) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create member

**Slug:** `MX_TECHNOLOGIES_CREATE_MEMBER`

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'

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Partner Account

**Slug:** `MX_TECHNOLOGIES_CREATE_PARTNER_ACCOUNT`

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.

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Fetch rewards

**Slug:** `MX_TECHNOLOGIES_FETCH_REWARDS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_guid` | string | Yes | The unique user identifier. Use either the MX-defined user GUID (prefixed with 'USR-') or your partner-defined user ID. |
| `member_guid` | string | Yes | The unique member identifier (prefixed with 'MBR-'). Obtain this from the List Members endpoint. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get configurable widget URL

**Slug:** `MX_TECHNOLOGIES_GET_CONFIGURABLE_WIDGET_URL`

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).

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `config` | object | Yes | Widget configuration options. At minimum, must specify the widget 'type'. |
| `user_guid` | string | Yes | The unique MX user GUID. Must start with 'USR-' prefix (e.g., 'USR-fa7537f3-48aa-a683-a02a-b18940482f54'). |
| `data_request` | object | No | Optional data aggregation request object for specifying products or additional data options. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Account Numbers by Member

**Slug:** `MX_TECHNOLOGIES_LIST_ACCOUNT_NUMBERS_BY_MEMBER`

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

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results (>=1). |
| `user_guid` | string | Yes | MX user GUID (must start with 'USR-'). |
| `member_guid` | string | Yes | MX member GUID (must start with 'MBR-'). |
| `records_per_page` | integer | No | Number of records per page (10-1000). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List account owners

**Slug:** `MX_TECHNOLOGIES_LIST_ACCOUNT_OWNERS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for paginated results (1-indexed). Defaults to 1 if not provided. |
| `user_guid` | string | Yes | MX-defined unique user identifier. Must start with 'USR-' prefix. |
| `member_guid` | string | Yes | MX-defined unique member identifier. Must start with 'MBR-' or 'MEM-' prefix. |
| `records_per_page` | integer | No | Number of records per page (10-1000). Defaults to 25 if not provided. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List accounts

**Slug:** `MX_TECHNOLOGIES_LIST_ACCOUNTS`

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

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results to return (1-based). |
| `use_case` | array | No | Filter accounts by member use cases: 'PFM' and/or 'MONEY_MOVEMENT'. |
| `is_manual` | boolean | No | Only include accounts that were manually created. |
| `user_guid` | string | Yes | MX user GUID (must start with 'USR-'). |
| `records_per_page` | integer | No | Number of records per page (10-1000). Defaults to MX default of 25. |
| `member_is_managed_by_user` | boolean | No | Only include accounts whose member is managed by the user. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List budgets

**Slug:** `MX_TECHNOLOGIES_LIST_BUDGETS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for paginated results. Defaults to 1 if not specified. |
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user. Obtain this from the List Users endpoint. |
| `records_per_page` | integer | No | Number of records per page (10-1000). Defaults to 25 if not specified. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List categories

**Slug:** `MX_TECHNOLOGIES_LIST_CATEGORIES`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results to return. Must be >= 1. |
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user. |
| `records_per_page` | integer | No | Number of records per page (10-1000). Defaults to 25. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List challenges

**Slug:** `MX_TECHNOLOGIES_LIST_CHALLENGES`

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

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for paginated results, must be >= 1. |
| `user_guid` | string | Yes | The unique identifier (GUID) for the MX user (prefix 'USR-'). |
| `member_guid` | string | Yes | The unique identifier (GUID) for the member. |
| `records_per_page` | integer | No | Number of records per page; valid range 10–1000 (default 25). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List favorite institutions

**Slug:** `MX_TECHNOLOGIES_LIST_FAVORITE_INSTITUTIONS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for pagination. Must be >= 1. Defaults to 1. |
| `iso_country_code` | array | No | Filter institutions by ISO country codes. Supported values: 'US' (United States), 'CA' (Canada), 'MX' (Mexico). |
| `records_per_page` | integer | No | Number of records per page. Valid range: 10-1000. Defaults to 25. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List goals

**Slug:** `MX_TECHNOLOGIES_LIST_GOALS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results to return. Must be >= 1. Defaults to 1. |
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user (e.g., 'USR-...'). |
| `records_per_page` | integer | No | Number of records per page (10-1000). Defaults to 25. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List institution credentials

**Slug:** `MX_TECHNOLOGIES_LIST_INSTITUTION_CREDENTIALS`

Tool to list credential fields required by a given institution. Use after selecting the institution code; supports optional pagination.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for pagination; must be >= 1. |
| `institution_code` | string | Yes | MX-defined code for the institution (e.g., 'mxbank'). |
| `records_per_page` | integer | No | Number of records per page for pagination; must be >= 1. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List institutions

**Slug:** `MX_TECHNOLOGIES_LIST_INSTITUTIONS`

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.

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List member accounts

**Slug:** `MX_TECHNOLOGIES_LIST_MEMBER_ACCOUNTS`

Tool 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results to return (1-based). |
| `user_guid` | string | Yes | MX user GUID (must start with 'USR-'). Obtain from LIST_USERS action. |
| `member_guid` | string | Yes | MX member GUID (must start with 'MBR-'). Obtain from LIST_MEMBERS action. |
| `records_per_page` | integer | No | Number of records per page. Defaults to MX default if not specified. |
| `member_is_managed_by_user` | boolean | No | Filter to accounts where the member is managed by the user (true) vs partner-managed (false). Omit to return all accounts. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List members

**Slug:** `MX_TECHNOLOGIES_LIST_MEMBERS`

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.

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List rewards

**Slug:** `MX_TECHNOLOGIES_LIST_REWARDS`

Lists rewards and loyalty program data for a specific member. Returns information about points, miles, and other rewards balances from connected financial institutions. Requires valid user_guid (from List Users) and member_guid (from List Members). Supports pagination for large result sets.

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List statements by member

**Slug:** `MX_TECHNOLOGIES_LIST_STATEMENTS_BY_MEMBER`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for pagination (1-indexed). Omit to get the first page. |
| `user_guid` | string | Yes | The unique MX user identifier. Must start with 'USR-' prefix. Obtain from LIST_USERS action. |
| `member_guid` | string | Yes | The unique MX member identifier. Must start with 'MBR-' prefix. Obtain from LIST_MEMBERS action for the user. |
| `records_per_page` | integer | No | Number of statements to return per page (10-1000). Defaults to 25 if not specified. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List taggings

**Slug:** `MX_TECHNOLOGIES_LIST_TAGGINGS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number for paginated results. Starts at 1. If not provided, defaults to the first page. |
| `user_guid` | string | Yes | The unique MX user identifier (starts with 'USR-'). Required to identify which user's taggings to retrieve. |
| `records_per_page` | integer | No | Number of records to return per page (max 1000). If not provided, the API uses its default. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List tags

**Slug:** `MX_TECHNOLOGIES_LIST_TAGS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results to return (1-indexed). Defaults to 1 if not specified. |
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user whose tags to list. Must start with 'USR-' prefix. |
| `records_per_page` | integer | No | Number of records per page (1-1000). Defaults to 25 if not specified. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List transactions

**Slug:** `MX_TECHNOLOGIES_LIST_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.

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List transactions by member

**Slug:** `MX_TECHNOLOGIES_LIST_TRANSACTIONS_BY_MEMBER`

Tool to list transactions for a member. Use when you have valid user and member GUIDs and need their transactions.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `page` | integer | No | Page number of results to return (1-based). |
| `to_date` | integer | No | Unix timestamp to filter transactions to this date (midnight); defaults to 5 days forward. |
| `includes` | string | No | Comma-separated list of enhancements: repeating_transactions,merchants,classifications,geolocations |
| `from_date` | integer | No | Unix timestamp to filter transactions from this date; defaults to 120 days ago. |
| `user_guid` | string | Yes | MX user GUID (must start with 'USR-'). |
| `member_guid` | string | Yes | MX member GUID (must start with 'MBR-' or 'MEM-'). |
| `to_timestamp` | integer | No | Unix timestamp to filter transactions to created time. |
| `to_created_at` | integer | No | Unix timestamp to filter transactions to created-at. |
| `to_updated_at` | integer | No | Unix timestamp to filter transactions to updated-at. |
| `from_timestamp` | integer | No | Unix timestamp to filter transactions from created time. |
| `from_created_at` | integer | No | Unix timestamp to filter transactions from created-at. |
| `from_updated_at` | integer | No | Unix timestamp to filter transactions from updated-at. |
| `records_per_page` | integer | No | Number of records per page (10-1000). Defaults to MX default of 25. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List users

**Slug:** `MX_TECHNOLOGIES_LIST_USERS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `id` | string | No | Filter by partner-defined user ID. |
| `page` | integer | No | Page number for paginated results (>=1). |
| `email` | string | No | Filter by user email. |
| `is_disabled` | boolean | No | Filter to only disabled users. |
| `records_per_page` | integer | No | Number of records per page (10-1000). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read account

**Slug:** `MX_TECHNOLOGIES_READ_ACCOUNT`

Tool to retrieve details for a specific account. Use after obtaining valid user and account GUIDs to fetch up-to-date account information.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user. |
| `account_guid` | string | Yes | The unique identifier (GUID) of the account. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read category

**Slug:** `MX_TECHNOLOGIES_READ_CATEGORY`

Tool to retrieve a default category by GUID. Use after confirming the default category GUID.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `category_guid` | string | Yes | The unique identifier (GUID) of the default category to retrieve. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read FDX account

**Slug:** `MX_TECHNOLOGIES_READ_FDX_ACCOUNT`

Retrieve details for a specific account using the FDX 4.6 standard API. This action fetches comprehensive account information including balances, status, and account attributes. It requires an FDX account identifier. AUTHENTICATION: This endpoint requires OAuth Bearer token authentication obtained from the MX Data Access OAuth flow. Basic Auth credentials for the MX Platform API will not work with FDX endpoints. FALLBACK: If FDX endpoints fail and the account_id looks like an MX Platform GUID (starts with 'ACC-' or 'ACT-'), the action will attempt to use the MX Platform API to retrieve the account instead.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `accountId` | string | Yes | 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

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read institution

**Slug:** `MX_TECHNOLOGIES_READ_INSTITUTION`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `institution_code` | string | Yes | A unique identifier for each institution, defined by MX. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read transaction

**Slug:** `MX_TECHNOLOGIES_READ_TRANSACTION`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user, starting with 'USR-'. |
| `transaction_guid` | string | Yes | The unique identifier (GUID) of the transaction, starting with 'TRN-'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read transaction by account

**Slug:** `MX_TECHNOLOGIES_READ_TRANSACTION_BY_ACCOUNT`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `includes` | string | No | 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' |
| `Accept_Version` | string | No | MX Platform API version (e.g., 'v20250224'). This header is required for API calls. |
| `user_identifier` | string | Yes | Use either the user `id` you defined or the MX-defined user `guid`. See MX-Defined GUIDs vs IDs Defined by You. |
| `member_identifier` | string | Yes | Use either the member `id` you defined or the MX-defined member `guid`. See MX-Defined GUIDs vs IDs Defined by You. |
| `account_identifier` | string | Yes | Use either the account `id` you defined or the MX-defined account `guid`. See MX-Defined GUIDs vs IDs Defined by You. |
| `transaction_identifier` | string | Yes | Use either the transaction `id` you defined or the MX-defined transaction `guid`. See MX-Defined GUIDs vs IDs Defined by You. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Read transaction rule

**Slug:** `MX_TECHNOLOGIES_READ_TRANSACTION_RULE`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_guid` | string | Yes | The unique identifier for a `user`, beginning with the prefix `USR-`. |
| `transaction_rule_guid` | string | Yes | The unique id for a `transaction_rule`, beginning with the prefix `UTR-`. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update transaction

**Slug:** `MX_TECHNOLOGIES_UPDATE_TRANSACTION`

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

#### Input Parameters

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

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update transaction rules

**Slug:** `MX_TECHNOLOGIES_UPDATE_TRANSACTION_RULES`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `user_guid` | string | Yes | The unique identifier (GUID) of the MX user. Must start with 'USR-' prefix. |
| `transaction_rule` | object | Yes | Transaction rule object containing fields to update. At least one field must be provided. |
| `transaction_rule_guid` | string | Yes | The unique identifier (GUID) of the transaction rule to update. Must start with 'UTR-' prefix. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update user tagging

**Slug:** `MX_TECHNOLOGIES_UPDATE_USERS_TAGGINGS`

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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `tagging` | object | Yes | Tagging object containing the new tag_guid to associate with the transaction. |
| `user_guid` | string | Yes | The unique identifier for the user, must start with 'USR-' prefix. |
| `tagging_guid` | string | Yes | The unique identifier for the tagging to update, must start with 'TGN-' prefix. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |