秋田预测市场 · Discord 审计

GMRl00K参与话题 1消息总数 4

该用户的聊天记录定位。

Reset

聊天记录

共 4 条,显示第 1-4 条
GMRl00K 2026-06-02 07:16:37 Polymarket

Use SDK that’s what I used

Use SDK that’s what I used

GMRl00K 2026-06-02 00:15:09 Polymarket API停止返回Token ID导致下单工具失效

Any help guys <@624575779023355904> messaged you in group chat I’m @tradesgmr on telegram The previously exposed Yes TokenId and No TokenId in market discovery responses, now the Market tools no longer return outcome token IDs, blocking all order placement via create_and_post_order and related trading tools as no token id no trading. Working currently list_positions returns Token Id for existing positions. list_markets, search, fetch_market, fetch_event, and read_resource polymarket://markets do not return Yes TokenId or No TokenId. list_markets and other discovery tools still return only: Id, Condition Id, Slug, prices, volume, liquidity, status, end date, image. No Yes TokenId, No TokenId, tokens array, or outcomes object containing token IDs. Impact As it seems we can’t get market discovery cannot obtain the required tokenId. (1/2) Order placement tools (mcp_polymarket_create_and_post_order, place_limit_order, place_market_order, etc.) cannot be called. Only markets where a position was previously opened (and tokenId captured from list_positions) can be traded. market.outcomes.yes.tokenId market.outcomes.no.tokenId market.tokens[] array with tokenId + outcome/side fields Please confirm if and Whether tokenId for Yes/No outcomes is still intended to be present on market objects returned by the Gamma / CLOB data layer. The correct canonical path to obtain tokenId for a market outcome in the current SDK version. Whether a separate endpoint or parameter is now required to retrieve outcome token IDs I am confused at this point As you know am using https://github.com/Polymarket/ts-sdk

Any help guys <@624575779023355904> messaged you in group chat I’m @tradesgmr on telegram The previously exposed Yes TokenId and No TokenId in market discovery responses, now the Market tools no longer return outcome token IDs, blocking all order placement via create_and_post_order and related trading tools as no token id no trading. Working currently list_positions returns Token Id for existing positions. list_markets, search, fetch_market, fetch_event, and read_resource polymarket://markets do not return Yes TokenId or No TokenId. list_markets and other discovery tools still return only: Id, Condition Id, Slug, prices, volume, liquidity, status, end date, image. No Yes TokenId, No TokenId, tokens array, or outcomes object containing token IDs. Impact As it seems we can’t get market discovery cannot obtain the required tokenId. (1/2) Order placement tools (mcp_polymarket_create_and_post_order, place_limit_order, place_market_order, etc.) cannot be called. Only markets where a position was previously opened (and tokenId captured from list_positions) can be traded. market.outcomes.yes.tokenId market.outcomes.no.tokenId market.tokens[] array with tokenId + outcome/side fields Please confirm if and Whether tokenId for Yes/No outcomes is still intended to be present on market objects returned by the Gamma / CLOB data layer. The correct canonical path to obtain tokenId for a market outcome in the current SDK version. Whether a separate endpoint or parameter is now required to retrieve outcome token IDs I am confused at this point As you know am using https://github.com/Polymarket/ts-sdk