Skip to main content
PUT
Set auto-redeem

Authorizations

X-Auth-Apikey
string
header
required

HMAC-signed API key. Send X-Auth-Apikey, X-Auth-Nonce and X-Auth-Signature.

Body

application/json
enabled
boolean
required

Turn auto-redeem on or off. Relay setApprovalForAll(auto_redeemer_address, enabled) from your Safe first — the chain is read back before this is stored.

Example:

true

Response

auto_redeemer_address
string | null
required

The contract to approve with setApprovalForAll on the Conditional Tokens. It can only redeem your resolved positions and return the whole payout to your Safe. Null when auto-redeem is not offered.

Example:

"0x4Fd2…"

available
boolean
required

Whether this account can use auto-redeem.

Example:

true

blockchain_key
string
required
Example:

"polygon-mainnet"

chain_id
number
required
Example:

137

conditional_tokens_address
string
required

Gnosis' Conditional Tokens — where your collateral actually sits.

Example:

"0x4D97DCd97eC945f40cF65F87097ACe5EA0476045"

domain_name
string
required

The EIP-712 domain name this exchange was DEPLOYED with. Hashed into every order signature, and different per network — sign with the served value, never a hard-coded one, or the signature will not recover.

Example:

"Calibri CTF Prediction Markets"

enabled
boolean
required

Whether resolved winnings are redeemed into your Safe automatically.

Example:

false

exchange_address
string
required

This deployment's CTF Exchange.

Example:

"0xB6Ac44d5A6388b8C7511F2fb20C0c03fD0CeDC83"

owner_address
string | null
required

What owns the Safe: your wallet EOA, or for a passkey member the secp256r1 signer contract. Served so a client can spot that a different wallet is connected — only the owner can sign for the Safe.

Example:

"0xE1188438C85C98aADFf1a88f97764E607B4978C3"

proxy_address
string | null
required

Your Safe — the deposit destination and the maker on your orders.

Example:

"0x0DECE7d83f8D47CD8dD8278c0F22c361C58577BD"

safe_status
enum<string>
required

The single field that answers "can this member trade?". setup_required means an order would REST AND THEN FAIL TO SETTLE — worse than being rejected, so do not trade on it.

Available options:
ready,
setup_required,
error,
unavailable,
unlinked
Example:

"ready"

session_keys_enabled
boolean
required

Whether this deployment has session trading keys switched on.

Example:

true

signature_type
enum<number>
required

How this account signs orders: 2 = POLY_GNOSIS_SAFE (Safe owned by your wallet), 3 = POLY_1271 (Safe owned by a passkey). Sign the way your type requires. Whether the Safe is usable yet is safe_status, not this field.

Available options:
2,
3
Example:

2

usdc_address
string
required

The collateral token.

Example:

"0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359"

safe_setup
object