Polytoolhub
What is Polymarket Relayer API?
The Relayer handles wallet transactions rather than CLOB order matching. It is used when connecting an existing account or creating supported Deposit Wallets and executing gasless wallet actions. The correct setup depends on the account wallet type and whether you are acting for an existing user or as a builder creating accounts.
Who it is for
- Developers integrating wallet setup and position settlement
- Builders creating supported user accounts
- Applications handling approvals, splits, merges and redemptions
Features and coverage
- Available on
- REST API
- Markets & venues
- Polymarket
- Gasless wallet operations
Submit supported authorized transactions through the relayer.
- Existing-account connection
Use the account wallet address and a Relayer API key.
- Builder account creation
Builder credentials support creation of signer-controlled Deposit Wallets.
- Wallet identity
Resolve signer, account wallet and wallet type explicitly.
- Position operations
Use the supported split, merge and redemption pathways.
- Approval and transfer actions
Manage the wallet actions needed around trading.
Workflows with Polymarket Relayer API
Connect an existing account
Identify the wallet type, create its Relayer API key through settings and initialize the secure client. Inspect the resolved signer and wallet before requesting an operation.
Build onboarding
Use server-side builder credentials to create the user’s Deposit Wallet, then preserve the signer-to-wallet mapping for later account actions.
Pricing and total cost
The relayer supports gasless wallet operations so the account does not need POL for those actions. This does not remove venue trading fees or external funding costs.
Getting started
Before you start: A signer address and account wallet address can differ.
- Determine whether the account uses a Deposit Wallet, legacy Proxy or Safe.
- For an existing account, create the Relayer API key in account settings.
- For account creation, use the builder credentials and documented secure-client flow.
- Inspect the resolved account identity.
- Submit only the supported transaction required by your workflow.
Useful links
What to check
- A signer address and account wallet address can differ.
- Relayer credentials and CLOB credentials authorize different operations.
- Builder credentials belong on the server, not in a browser bundle.
- Gasless support applies to the documented wallet operations, not every external transfer.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Write a review
How was your experience with Polymarket Relayer API?
Share what you used, what worked and what could be better. We confirm your email and review the submission before publishing.
To submit a review, email info@polytradingbot.com with the tool name, your rating and your experience. Enable JavaScript to prepare a draft here.
Related tools
Browse category
The official TypeScript SDK for public market data, typed pagination, real-time subscriptions and authenticated trading and wallet actions.
- Language TypeScript · JavaScript
Read Polymarket prices and order books or build authenticated order placement, cancellation and account-order management.
- Data coverage Prices · Order books
- Access API
The official Python client for typed Polymarket data, sync or async account workflows, streaming and notebook-friendly analysis.
- Language Python
Frequently asked questions about Polymarket Relayer API
Is this the endpoint for placing a limit order?
No. CLOB handles orders; the Relayer handles wallet transactions.
Why does my account wallet differ from the signer?
Smart-wallet accounts separate the controlling signer from the wallet holding positions.
Do users need POL for supported relayed actions?
The documented gasless route removes that requirement.