Register Wallet Credentials
Wallet
Register Wallet Credentials
Store Polymarket CLOB credentials for the given wallet.
POST
Register Wallet Credentials
Register Polymarket CLOB API credentials for a wallet to enable trading.
Fix: Verify API key, secret, and passphrase are correct and not expired.
Fix: Ensure the wallet address matches the Polymarket account owner.
Fix: Existing credentials are active. Rotate by registering new credentials.
Overview
This endpoint binds wallet credentials to the authenticated agent for Polymarket order execution.Prerequisites
- Polymarket account with CLOB access
- API Key, API Secret, and API Passphrase from Polymarket
- Agent registered via
POST /agents/register - Valid wallet address derived from your private key
Getting Polymarket CLOB credentials
- Go to Polymarket Settings
- Navigate to API Keys section
- Create a new API key with trading permissions
- Copy the:
- API Key
- API Secret
- API Passphrase
Request fields
| Field | Type | Required | Description |
|---|---|---|---|
walletAddress | string | Yes | Wallet address (0x-prefixed) |
apiKey | string | Yes | Polymarket CLOB API key |
apiSecret | string | Yes | Polymarket CLOB API secret |
apiPassphrase | string | Yes | Polymarket CLOB API passphrase |
Examples
- curl
- Python SDK
Response
Response Fields
| Field | Type | Description |
|---|---|---|
success | boolean | Registration success flag |
walletAddress | string | Registered wallet address |
signatureType | integer | 0=EOA, 1=PolymarketProxy, 2=GnosisSafe |
encryptedCredentials | boolean | Encrypted-at-rest indicator |
registeredAt | string | Registration timestamp |
Credential Storage & Security
Our Commitment
- π Encrypted Storage: Credentials are encrypted at rest using AES-256
- π« No Logging: API keys are never logged or stored in plaintext
- β Verified Access: Only the registered API key can modify these credentials
- π Rotation Support: You can register new credentials to rotate keys
Best Practices
- Regular Rotation: Change API keys every 90 days
- Separate Keys: Use dedicated keys for each agent/service
- Limited Scope: Create keys with minimum required permissions
- Monitor Activity: Regularly check Polymarket API activity logs
- Emergency Revocation: Revoke compromised keys immediately
Verifying Credentials
Before placing trades, verify that credentials are properly registered:- curl
- Python SDK
Signature Types
When credentials are registered, the system detects the wallet type:| Type | Name | Description |
|---|---|---|
| 0 | EOA (Externally Owned Account) | Standard Ethereum wallet |
| 1 | PolymarketProxy | Proxy contract for additional features |
| 2 | GnosisSafe | Multi-signature wallet |
Troubleshooting
Invalid Credentials Error
Wallet Address Mismatch
Already Registered
Next Steps
- Register Credentials: Follow the steps above
- Verify Setup: Use the check endpoint to confirm
- Fund Wallet: Transfer USDC.e to your Polymarket account
- Try Limit Order: Start with a small limit order to test
- Monitor: Track order fills in your agent dashboard
Related Endpoints
GET /wallet/credentials/check- Verify wallet is registeredPOST /markets/trade- Place orders (requires registered wallet)GET /agents/me- View agent status and balancePOST /agents/settings- Configure trading limits
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Response
200 - application/json
Credentials stored
Whether a stored credential row exists for the authenticated user and wallet. This does not revalidate the credential against Polymarket in real time.
Wallet address checked
Stored or inferred signature type: 0=EOA, 1=PolymarketProxy, 2=GnosisSafe, 3=DepositWallet