聊天记录
共 7 条,显示第 1-7 条
I wrote an API integration program and ran a test order submission. I sent the following json structure, but the response returned "Invalid order payload." Does anyone know why?
```
{
"order":
{
"salt": "2026062400000001",
"maker": "<funder address>",
"signer": "<signer address>",
"tokenId": "25816453004493430703111310222915530050775468247675765026246375792528815294593",
"makerAmount": "300000",
"takerAmount": "1000000",
"expiration": "0",
"side": "BUY",
"signatureType": 3,
"timestamp": "1782270778834649",
"metadata": "0x0000000000000000000000000000000000000000000000000000000000000000",
"builder": "0x0000000000000000000000000000000000000000000000000000000000000000",
"signature": "<EIP-712 signature>"
},
"owner": "<apikey>",
"orderType": "GTC",
"postOnly": false
}
```
I am a new user so I use `signatureType = 3(POLY_1271)` as api document described.
I wrote an API integration program and ran a test order submission. I sent the following json structure, but the response returned "Invalid order payload." Does anyone know why?
```
{
"order":
{
"salt": "2026062400000001",
"maker": "<funder address>",
"signer": "<signer address>",
"tokenId": "25816453004493430703111310222915530050775468247675765026246375792528815294593",
"makerAmount": "300000",
"takerAmount": "1000000",
"expiration": "0",
"side": "BUY",
"signatureType": 3,
"timestamp": "1782270778834649",
"metadata": "0x0000000000000000000000000000000000000000000000000000000000000000",
"builder": "0x0000000000000000000000000000000000000000000000000000000000000000",
"signature": "<EIP-712 signature>"
},
"owner": "<apikey>",
"orderType": "GTC",
"postOnly": false
}
```
I am a new user so I use `signatureType = 3(POLY_1271)` as api document described.
I am a new user utilizing the POLY_1271=3 signature, but the API's `place order` endpoint indicates support only for types 0, 1, and 2. What value should I specify signatureType when placing an order via the API?
I am a new user utilizing the POLY_1271=3 signature, but the API's `place order` endpoint indicates support only for types 0, 1, and 2. What value should I specify signatureType when placing an order via the API?
Hi, I generated an API key, secret, and passphrase at `https://polymarket.com/settings?tab=builder` and connected to `wss://ws-subscriptions-clob.polymarket.com/ws/user`. However, after connected and sent the auth message `{"auth":{"apiKey":"...","secret":"...","passphrase":"..."},"type":"user"}`, the connection was immediately closed by remote with error ABNORMAL_CLOSURE. Does anyone know why?
Hi, I generated an API key, secret, and passphrase at `https://polymarket.com/settings?tab=builder` and connected to `wss://ws-subscriptions-clob.polymarket.com/ws/user`. However, after connected and sent the auth message `{"auth":{"apiKey":"...","secret":"...","passphrase":"..."},"type":"user"}`, the connection was immediately closed by remote with error ABNORMAL_CLOSURE. Does anyone know why?
Is market websocket ping message valid? I sent `{}` as ping but received `INVALID OPERATION` rather than pong message.
Is market websocket ping message valid? I sent `{}` as ping but received `INVALID OPERATION` rather than pong message.
Has the API recently changed its signature method? We're getting an L1 error during pre-launch test orders: "User or API Wallet 0xce... does not exist." Orders were successful in both the testnet and production previously.
Has the API recently changed its signature method? We're getting an L1 error during pre-launch test orders: "User or API Wallet 0xce... does not exist." Orders were successful in both the testnet and production previously.
Will the number value of the condition id and market id, as well as the order of the token id, change in the API information? Or are they fixed after generation?
Will the number value of the condition id and market id, as well as the order of the token id, change in the API information? Or are they fixed after generation?
Will the number value of the condition id and market id, as well as the order of the token id, change in the API information? Or are they fixed after generation?
Will the number value of the condition id and market id, as well as the order of the token id, change in the API information? Or are they fixed after generation?