Skip to main content
The Polymarket Exchange exposes all API functionality via gRPC using Protocol Buffers. This section covers unary (request/response) methods - for streaming services, see gRPC Streaming.

Why Use gRPC?

gRPC offers several advantages over REST:
  • Performance: Binary protocol with smaller payloads and faster serialization
  • Type Safety: Strongly-typed messages defined in Protocol Buffers
  • Streaming: Native support for bidirectional streaming (covered in gRPC Streaming tab)
  • Code Generation: Auto-generate client libraries in any language

Download Proto Files

Get the complete Protocol Buffer definitions to generate client libraries in any language

Server Endpoints

Development Environment (dev01)

Pre-Production Environment

Production Environment

All gRPC connections use TLS/SSL. Ensure your client is configured for secure connections.

Authentication

All gRPC calls require an access token passed in the authorization metadata header:
See Authentication for details on obtaining access tokens.

Available Services

Trading Services

Market Data Services

Account Services

Funding Services

Execution Feed


Drop Copy & Trade Capture gRPC Streaming

The DropCopyAPI service provides real-time streaming endpoints for execution reports, trade capture, and position changes. These are gRPC streaming only - there are no REST equivalents.
For complete documentation including code examples, see DropCopy & Trade Capture Streaming.

Available Streaming Endpoints

Drop Copy Subscription

Stream execution reports as they occur for your firm. Use this for:
  • Real-time order execution monitoring
  • Fill notifications across all firm accounts
  • Cancel and reject tracking
Key parameters:
  • symbols - Filter by specific symbols (empty = all)
  • resume_token - Resume from previous position after disconnect

Trade Capture Report Subscription

Stream completed trades for reconciliation and compliance. Each trade contains:
  • aggressor - The incoming (taker) execution
  • passive - The resting (maker) execution
  • trade_type - Type of trade (REGULAR, CROSS, etc.)
  • state - Trade state (NEW, CLEARED, BUSTED, …); see Trade States

Quick Example

When to Use Each Stream

Package Structure

All services are in the polymarket.v1 package:

Quick Start

1. Install gRPC Libraries

2. Obtain Proto Files

Download the proto files directly: polymarket-protos.zip Use the downloaded definitions as the client contract. Do not make client startup depend on server reflection, whose availability can differ by environment.

3. Generate Client Code

4. Make Your First Call

REST vs gRPC

Both REST and gRPC access the same underlying services. Choose based on your needs:
Most integrations use REST for simplicity and gRPC for performance-critical paths like order entry.

Next Steps

gRPC Streaming

Real-time market data and order subscriptions

Authentication

Access token setup for gRPC

REST API

Equivalent REST endpoints

Proto Reference

Proto message definitions