SecureClient.create() order placement rejected on every wallet type: 'maker address not allowed' (EOA + Safe) / 'order signer address has to be the address of the API KEY' (Deposit Wallet)

[byronyip98]

Summary

Every order placement attempt via SecureClient.place_market_order() (polymarket-client 0.1.0b13, the latest release on PyPI as of 2026-07-03) is rejected by the CLOB API, across all three wallet types the SDK supports. No workaround found after 6 independent attempts across 2 days.

Environment

• polymarket-client==0.1.0b13 (latest on PyPI)
• Python 3.11
• Polygon mainnet, real funded wallet ($8.99 USDC + 29.93 POL, confirmed on Polygonscan)

Reproduction — 3 wallet configurations tried, all fail differently

1. wallet=<existing GNOSIS_SAFE address> (from a wallet already onboarded via polymarket.com browser trading, holding real funds):

polymarket.errors.RequestRejectedError: maker address not allowed, please use the deposit wallet flow

2. wallet=None (SDK auto-derives/deploys the Deposit Wallet per docstring: "Defaults to the signer's Deposit Wallet"):

• Client construction succeeds, Deposit Wallet deploys (after adding a RelayerApiKey — separate issue, Gasless transactions require a Builder API Key or Relayer API Key is raised without one).
• Every subsequent order is then rejected:

polymarket.errors.RequestRejectedError: the order signer address has to be the address of the API KEY

• This matches the root cause described in Polymarket/py-clob-client-v2#71 and siblings (Drop unsupported tag/series request params and response fields #64, fix(gamma): default list_events to open events #70, ci: publish releases from release please #75, fix(gamma): preserve event published timestamp #77): create_or_derive_api_key() binds the L2 API key to the signer EOA, while a Deposit Wallet order's funder_address (maker) is the deposit wallet — the server rejects the mismatch on every single order.

3. wallet=<signer's own EOA address> (plain EOA, signature_type=0, the simplest/original order type where signer == maker):

polymarket.errors.RequestRejectedError: maker address not allowed, please use the deposit wallet flow

• Same rejection as configuration 1, despite signer == maker this time. Matches Polymarket/py-clob-client-v2#53, reported for even brand-new wallets, unresolved.

Expected behavior

At least one of the three documented wallet configurations should allow order placement to succeed.

Actual behavior

All three are rejected, for two different reasons that appear to contradict each other: configs 1 and 3 say "use the deposit wallet flow," but config 2 (the deposit wallet flow) is rejected by a client-credential-binding bug.

Why filing here specifically

The related issues (py-clob-client-v2 #53, #64, #70, #71, #75, #77) are filed against a different repository than the one that publishes polymarket-client (this repo, py-sdk, verified via PyPI package metadata). This repo's own tracker had no existing report of this failure as of 2026-07-06.

Happy to provide additional logs/reproduction detail — the pilot wallet involved is a small, disposable test wallet, not a production account, so debugging access isn't a concern on our end.

[cesarenaldi]

Thanks for reporting this and for the detailed repro. We will look into it.

[cesarenaldi]

We have tests for this path that do not surface the issue, and for good measure we added a metered integration test for the sync SecureClient here: #140.

We are aware of the related GitHub issues raised on the CLOB client repos. In our experience (I replied to many of these) many of these are often caused by confusion around which wallet value should be provided for each custody flow.

A few clarifying questions:

1. For wallet=<existing GNOSIS_SAFE address>: is this the Polymarket Safe proxy address? Can you share the address so we can check the account?

2. For wallet=None: this is intended for users who want to use the new Deposit Wallet flow. Since you already have a Safe, it is not clear whether this was run with a brand-new signer or with a signer tied to the existing Safe. Can you clarify which signer was used and whether you expected this to deploy a new Deposit Wallet or trade through the existing Safe?

   The Gasless transactions require a Builder API Key or Relayer API Key message is expected if the SDK is being asked to deploy a new Deposit Wallet without a Builder API Key. We are updating the docs so this is clearer in the coming weeks.

3. For wallet=<signer's own EOA address>: this is a very edge-case configuration. It does not rely on any Polymarket smart wallet to hold funds, so the EOA itself needs both POL for gas and pUSDC for trading. It is unlikely this is the scenario you want to use unless you specifically intend to trade directly from the EOA.

Can you share the address of the Polymarket wallet you intend to integrate with? That will let us take a look and give a more specific answer.