Existing MetaTrader 4 broker environments can include trade servers, access points, manager terminals, client terminals, public APIs, data feeds, gateways, CRM connections and reporting systems. New MT4 trading platform licenses are no longer sold, so this page describes the components, interfaces and maintenance boundaries of existing deployments.
An MT4 broker environment is more than the client terminal. Trade servers process accounts, quotes and trading requests; access points handle client connections; manager terminals support administration; client terminals display account and market data; feeds and gateways connect external data or execution services.
Trade servers handle account state, quotes, orders and trading requests. Access points connect client terminals to the server environment, while manager terminals provide account and operational controls inside the broker-managed infrastructure.
Manager tools can be used for account, permission and operational administration. CRM, reporting, support and other internal systems may handle separate customer or business processes outside the core trading server.
Existing MT4 brokers operate their own server environments and control administration, support, accounts and trading data. MetaQuotes states that it does not access broker servers, accounts or client trading history.
Existing branded MT4 environments can include client logos, terminal packages, server names, login paths and support workflows. These brand elements sit above the broker account and server layer. New MT4 platform licenses are no longer available for purchase, so this section only describes existing deployments.
Names, logos and client packages affect the user-facing layer, while account access still depends on server configuration and broker credentials. Changes to branded assets or entry points should preserve existing server and login paths.
When an existing MT4 environment changes domains, server addresses, client packages or connected systems, account login, quotes, order submission and client access should be tested separately. The work concerns an existing deployment rather than a newly licensed MT4 platform.
MT4 APIs serve different objects and responsibilities. Server API extends server processing, Manager API supports administrative functions, DataFeed API handles quote and news feeds, Report API produces account and financial reports, and WebServices API connects websites or other external systems.
Server API can extend server-side processing and plugin functions. Manager API is used for account, trade and administrative operations and can support custom management applications or internal system integration.
DataFeed API brings external quote and news data into MT4. Report API creates account and financial-operation reports, while WebServices API can expose account or quote data to websites and other business systems.
CRM, client portals and internal systems can exchange selected account, reporting or operational data through supported interfaces. Read and write permissions, source-of-truth rules and failure handling must be defined by the broker architecture.
Data feeds bring external quote or news data into MT4, while gateways connect the broker environment to external pricing or execution infrastructure. Both layers require server configuration, symbol mapping, update rules and error handling.
External quotes and news are converted into the format used by MT4 and distributed through the broker server to connected client terminals. The integration must define data formats, refresh behavior, symbol mapping and exception handling.
Gateways connect MT4 with external pricing, liquidity or execution environments. Routing logic, order handling, pricing sources and recovery behavior depend on the broker’s own infrastructure and configuration.
MT4 stores trading-account and server-side data, while CRM, client portals, reporting, payments and support systems may manage separate business processes. APIs connect these systems, but ownership of each data object and write path should remain explicit.
CRM may own customer records and business processes, MT4 may own trading-account and server data, and reporting systems may own derived outputs. Integration should define data origin, sync direction, write permissions and conflict handling.
Existing MT4 brokers remain responsible for server infrastructure, administration, account operations and support. MetaQuotes states that it does not have access to broker servers, accounts or client trading history.
Answers about existing MT4 server environments, licensing status, APIs, branded clients, data feeds, gateways, account data and back-office integration.
No. MetaQuotes states that new MetaTrader 4 trading platform licenses are no longer available for purchase. This page therefore describes existing licensed environments, their interfaces and maintenance responsibilities.
Existing MT4 environments can use Server API, Manager API, DataFeed API, Report API and WebServices API for server extensions, administrative tools, data feeds, reporting and external-system connections.
Data feeds bring quote or news data into MT4. Gateways connect the platform to external pricing, liquidity or execution infrastructure. Both depend on the broker’s own server configuration and mapping rules.
The broker operates and maintains its own MT4 server infrastructure and controls account administration, support and trading data. MetaQuotes states that it does not access broker servers, accounts or client trading history.
The broker environment contains servers, APIs, feeds and back-office systems, while client terminals handle quotes, charts, orders and account access. Terminal access options are listed on the download page, and end-user trading functions are described on the platform page.