MetaTrader®, MT4® and MT5® are trademarks of MetaQuotes Ltd. This is an independent service and is not affiliated with, authorized by, or endorsed by MetaQuotes. Trustpilot4.0
gRPC · TYPED & STREAMING

The same MetaTrader API — now over gRPC.

For latency-sensitive and high-throughput clients: typed messages, generated stubs and server-streaming, backed by the same terminal and the same key as REST and WebSocket. Point your client at the .proto and go.

Get the proto →Compare transports
metatraderapi.proto · Call + typed methods + streams
Typed messages & stubs Server-streaming quotes & trades Generic Call for every endpoint Same key as REST/WS
// what it is

One backend, three ways in.

The gRPC interface exposes the same MetaTrader API surface over Protocol Buffers, with typed request/response methods and server-streaming. You get generated client stubs in your language, compile-time-checked messages, and low-overhead binary framing — ideal for trading systems where latency and throughput matter. Alongside typed methods like AccountSummary, GetQuote and OrderSend, a generic Call method reaches every REST endpoint by name, and StreamQuotes / StreamTrades push data as it happens. Authentication uses the same key you already have, passed in gRPC metadata.

// pick your transport

Same account. Choose the interface that fits.

REQUEST / RESPONSE

REST

Simplest to call — plain HTTPS and JSON. Great for scripts, dashboards and back-office tools.

LIVE PUSH

WebSocket

Quotes, trades and connection state streamed the instant they change. Great for UIs and bots.

TYPED / HIGH-THROUGHPUT

gRPC

Typed stubs and server-streaming over Protocol Buffers. Great for latency-sensitive trading systems.

// who it's for

For systems that treat milliseconds as money.

Low-latency execution

Binary framing and persistent connections shave overhead off every order and quote.

Polyglot backends

Generate stubs in Go, Rust, Java, Python or C# from one proto and stay type-safe.

High-fan-out streaming

Server-streamed quotes and trades feed many symbols down one efficient channel.

// questions

Frequently asked

Is there a gRPC interface for the MetaTrader API?+
Yes. The same surface is available over gRPC with a published .proto: typed methods such as AccountSummary, GetQuote and OrderSend, a generic Call for any endpoint, and server-streaming for quotes and trades.
Why choose gRPC over REST or WebSocket?+
gRPC adds typed, generated stubs and low-overhead binary framing, which suits latency-sensitive and high-throughput trading systems. REST is simplest for scripts; WebSocket is best for live UI updates. All three hit the same account.
How do I authenticate a gRPC call?+
With the same API key you use for REST and WebSocket, passed in gRPC metadata along with the account id. No separate credential to manage.
Can I stream quotes and trades over gRPC?+
Yes. StreamQuotes pushes quote updates for the symbols you request, and StreamTrades pushes trade events as positions open and close, both as server-streams.
Which languages are supported?+
Any language with gRPC tooling — Go, Rust, Java, Python, C#, Node and more — since you generate the client stubs from the shared .proto file.
Start free

Generate a client and stream typed data.

Grab the proto, generate stubs in your language, and hit the same account you already use over REST.

Get an API key →Read the docs