KAkairos
Onboarding

Provision Polymarket CLOB credentials and set on-chain approvals

The one-time onboarding step for Polymarket. In a single call the server derives CLOB API credentials for your wallet (signing the ClobAuth EIP-712 message with your delegated key), encrypts and stores them, and sets the token approvals the venue needs. Until this succeeds, POST /orders on polymarket will fail. Credentials are never returned. The derived API key/secret/passphrase are stored server-side only — deliberately kept out of HTTP responses so they cannot leak through logs, proxies or browser devtools. Legacy-EOA users get gas sponsorship plus approvals here. Deposit-wallet users had their approvals set by the onboarding batch (POST /exchanges/polymarket/deposit-wallet/onboard), so the approval legs are skipped and the *_tx_hash fields are omitted. Auth & scope. Requires trade:execute for polymarket, wallet ownership, and the mutation gate — this provisions signing credentials and is in the same risk class as order submission.

post/exchanges/polymarket/enable-trading

Request

  • Base URL
    https://execution.kairos.trade
  • Auth
    API key in header X-Client-Id and API key in header X-Api-Key and API key in header X-Api-Secret

Request body

wallet_addressstring required

The wallet to enable. Must be a wallet owned by the authenticated caller.

Response

Credentials provisioned and approvals set.

successboolean required
messagestring required
usdc_tx_hashstring

OMITTED entirely (not null) when no USDC approval was needed.

ctf_tx_hashstring

OMITTED entirely (not null) when no CTF approval was needed.

Changes

No recorded changes to this operation across all 1 revision of this API.