What is Polymarket Relayer API?

The integration path depends on whether you connect an existing account or create a supported signer-controlled Deposit Wallet. Resolve the signer, account wallet and wallet type explicitly: the address controlling an account can differ from the address holding its positions.

Existing-account Relayer credentials and server-side Builder credentials serve different paths. They also differ from CLOB order credentials. Supported gasless wallet actions do not establish fee-free trading or external funding.

Who it is for

Integrating wallet setup and position settlement.
Creating supported user accounts.
Handling approvals, split, merge and redemption.

Features and coverage

Gasless submission
Send supported authorized wallet transactions through the Relayer.
Existing accounts
Use the account wallet address and its Relayer API key.
Builder onboarding
Builder credentials support signer-controlled Deposit Wallet creation.
Identity resolution
Determine signer, account wallet and wallet type before an action.
Position operations
Use the documented split, merge and redemption paths.
Approvals and transfers
Handle supported wallet actions around trading.
Submit limit
The published IP table specifies 25 requests per minute for /submit.

Workflows with Polymarket Relayer API

Connect an existing user

Establish which wallet type the existing account uses before setting up access. Obtain the corresponding Relayer key in account settings and initialize the secure client; use its resolved signer and wallet identities to check the operation you are about to request.

Create account onboarding

Keep Builder credentials on the server, create the supported Deposit Wallet and preserve signer-to-wallet mapping for later actions.

Pricing and total cost

Eligible relayed wallet actions do not require the account to hold POL for gas. This does not remove venue trading fees or external funding costs, nor establish zero service fees.

Getting started

Before you start: Relayer and CLOB credentials authorize different operations.

Determine Deposit Wallet, legacy Proxy or Safe account type.
For an existing account, use its settings to create the Relayer key.
For account creation, follow the documented Builder secure-client flow.
Inspect the resolved account identity.
Submit only the supported transaction your workflow requires.

Signer and account-wallet addresses may differ.

Relayer API base endpoint

Read position operations

Read Relayer submit reference

Useful links

What to check

Relayer and CLOB credentials authorize different operations.
Builder credentials must stay server-side, outside browser bundles.
Gasless support is limited to documented wallet actions, not every external transfer.
Use wallet-specific instructions rather than assuming a universal account payload.

A closer look

Ratings & reviews

Editorial rating

3.5/ 5

0 user reviews

PredictionToolkit editorial

Our take on Polymarket Relayer API

Gasless support reduces funding requirements for eligible wallet actions. Separate credentials and signer/account identities make this a developer integration needing clear account requirements.

Based on documented features, setup and access terms. How we rate