ceven

MX Technologies

Aggregates financial data from thousands of institutions into your workflows, monitors account balances in real time, and categorizes transactions for automated financial analysis.

Try MX Technologies in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native MX Technologies integration

    • Describe the outcome and Ceven picks the right MX Technologies calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your MX Technologies data, across all 36 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke MX Technologies access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in MX Technologies, when, and on whose behalf.
    • The agent pauses and asks when MX Technologies is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach MX Technologies.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every MX Technologies action to support review and sign off.

Supported tools

Every action Ceven's agents can run on MX Technologies, and when to use it.

List transactions
Pull the full transaction history for a user across all linked accounts. Use this to analyze spending patterns or detect income.
Read account balance
Pull the current available balance for a specific account using the user and account guids.
List institutions
Pull a list of all supported financial institutions. Use this to filter by country or product before starting a connection.
Get widget URL
Generate a configurable connection URL for a user to link their bank account via the MX interface.
List challenges
Retrieve pending MFA challenges for a member. Use this when an account is in a challenged state and needs user input.
Create member
Start aggregating financial products for a new member after you have gathered their connection credentials.
List accounts
Pull all accounts associated with a user guid to get a high level view of their financial footprint.
List budgets
Retrieve the active budgets for a specific user to compare actual spend against their goals.
List goals
Pull the financial goals set for a user to track progress toward specific savings targets.
List categories
Pull both default and custom transaction categories for a user to ensure consistent labeling.
Create account
Manually add an external or test account to a user record when an API connection is not available.
List users
Pull a paginated list of all user accounts with optional filters for administrative oversight.
Fetch rewards
Trigger an asynchronous job to aggregate rewards data for a specific member.
List statements
Pull available bank statements for a specific member using their user and member guids.
Cancel Partner Account
Tool to cancel (disable) a client account under a partner account. this maps to mx platform api: put /users/{guid} with body {"user": {"is disabled": true, "metadata": "..."}}.
Retrieve 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 → a
Create Partner Account
Tool to create a new client account under a partner account. use when provisioning a new constant contact client after obtaining api key and jwt authorization.
Create Partner Account User SSO
Tool to create a new partner account user with single sign on enabled. use when adding an sso user under a partner client account with 'sso for all users' enabled.
Get configurable widget URL
Tool to retrieve a configurable widget url for a user. use after determining the user guid.
List Account Numbers by Member
Tool to list account numbers for a specific member. use after obtaining user and member guids.
List account owners
Tool to list account owners associated with a member's account. use after validating user and member guids.
List account owners by member
Tool to list account owners for a specific member. use when you have the user guid and member guid.
List Connect Widget URLs
Tool to list connect widget urls for a user. use when you need to retrieve all connect widget urls associated with a user.
List favorite institutions
Tool to list partner favorite institutions, sorted by popularity. use when you need to retrieve a paginated set of a partner's favorite institutions.
List institution credentials
Tool to list credential fields required by a given institution. use after selecting the institution code; supports optional pagination.
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.
List members
Tool to list members associated with a specific user. use when you need to retrieve the members for a given user guid.
List rewards
Tool to list rewards associated with a specific user and member. use after confirming both user guid and member guid; supports pagination.
List statements by member
Tool to list statements for a member. use after obtaining valid user and member guids.
List taggings
Tool to list all taggings for a specific user. use when you need to fetch taggings associated with a user after obtaining their user guid.

30 actions · scroll to see them all

Frequently asked questions

When a financial institution requires multi factor authentication, the account enters a challenged state. Ceven uses the List challenges action to detect these events and pull the specific prompts required by the bank. The agent then routes these prompts to your end user through your preferred communication channel, such as an email or an in app notification. Once the user provides the code, the agent submits it back to MX to restore the data flow. This prevents the workflow from simply failing and allows for a graceful recovery of the connection without requiring the user to restart the entire onboarding process from scratch.
Yes, Ceven can interact with the category system to ensure your financial data matches your specific business logic. By using the List categories action, the agent identifies existing labels and can then map incoming transactions to those categories. If you have a specific taxonomy for wealth management or corporate accounting, the agent can be instructed to tag transactions based on keywords or merchant IDs. This ensures that when you run a report on spending, the data is clean and categorized according to your internal rules rather than relying solely on the default labels provided by the banking institution.
In the MX architecture, a user guid represents the top level identity of the person using your application. A member guid is a more granular identifier used when that user connects to one or more financial institutions. A single user can have multiple members if they are linking accounts across different banks or product types. Ceven manages this hierarchy automatically. When you ask the agent to pull transactions, it first resolves the user guid to find all associated member guids, then iterates through those members to aggregate a complete transaction history across the entire financial profile of that individual.
Ceven automates the generation of the Connect Widget URL. Instead of you manually constructing the URL with various parameters, the agent calls the Get configurable widget URL action using the user guid. This generates a secure, temporary link that you can send directly to your client. Once the client completes the authentication flow within the MX widget, the bank grants access to the data. Ceven then detects the successful connection via a webhook or a polling interval and immediately begins the initial backfill of account balances and transaction history into your designated data store.
Yes, MX Technologies enforces rate limits that vary based on your specific subscription tier and the endpoints you call. For example, heavy polling of the Read account balance endpoint across thousands of users can trigger a 429 Too Many Requests response. Ceven handles this by implementing an exponential backoff strategy, meaning the agent will automatically pause and retry the request after a short delay. However, for very large datasets, we recommend using a scheduled batch workflow rather than real time triggers to avoid hitting these limits during peak hours and ensuring a stable data pipeline.
Ceven acts as a secure conduit for the data returned by the MX API. We do not store the raw bank login credentials, as those are handled directly between the user and MX via the secure widget. The financial data retrieved by the agent is encrypted in transit using TLS and encrypted at rest using AES 256. You can define fine grained permissions within Ceven to control which agents have access to sensitive financial data. For instance, you can allow a reporting agent to see aggregated balances while preventing it from seeing individual transaction descriptions, ensuring a strict need to know access model.
Yes, once a user successfully connects their account via the MX widget, Ceven can initiate a historical pull. Depending on the institution and the permissions granted, MX typically allows access to several months or years of past transactions. The agent uses the List transactions action with a specified date range to backfill your database. If the institution requires a separate consent for historical data, the agent will flag this as a requirement and can prompt the user to provide additional authorization through the MX interface to ensure no gaps exist in the financial history.

Alternatives to MX Technologies

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Plaid logoPlaidYodlee logoYodleeTink logoTinkSalt Edge logoSalt Edge

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect MX Technologies and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free