Limitless API 订单簿在 FUNDED 状态下返回错误

Hi, I'm working on integrating with the Limitless API for BTC 5-minute markets, and we need to verify the correct way to read the public order book. From the market detail endpoint, we see the current market in the FUNDED state; we have the marketSlug, yes_token/no_token, and price display, but when calling the public order book endpoint in the format /markets/{marketSlug}/orderbook, we receive a 400 response {"message":"Market is not active"}. The documentation states that public market reads and order books can be called unauthenticated. Could you please confirm the exact endpoint and parameters we should use to read the executable order book depth for these BTC 5-minute markets? We are primarily interested in whether the order book functions only in the OPEN/ACTIVE state or should already function in the FUNDED state, whether it should be called via marketSlug or tokenId, and how to correctly read the YES/NO order book for GTC post-only maker orders. Thank you.

Hi, I'm working on integrating with the Limitless API for BTC 5-minute markets, and we need to verify the correct way to read the public order book. From the market detail endpoint, we see the current market in the FUNDED state; we have the marketSlug, yes_token/no_token, and price display, but when calling the public order book endpoint in the format /markets/{marketSlug}/orderbook, we receive a 400 response {"message":"Market is not active"}. The documentation states that public market reads and order books can be called unauthenticated. Could you please confirm the exact endpoint and parameters we should use to read the executable order book depth for these BTC 5-minute markets? We are primarily interested in whether the order book functions only in the OPEN/ACTIVE state or should already function in the FUNDED state, whether it should be called via marketSlug or tokenId, and how to correctly read the YES/NO order book for GTC post-only maker orders. Thank you.

Feel free to dm me to talk about this further Your detail payload's status: FUNDED and the orderbook's readiness are governed by different fields. FUNDED can be present even while a slot is not yet OPEN — so it tells you nothing about whether the book is readable. The book is gated purely by the slot's state == "OPEN" && tradable == true from the timeline endpoint. So: - Stop gating on status from get-market. It doesn't expose tradable. - Drive off GET /markets/timeline, take the slot whose state == "OPEN" and tradable == true, use that slot's slug for GET /markets/{slug}/orderbook. The doc text for the timeline slug field says this explicitly ("use it to fetch the orderbook… once tradable"). - For pre-warming the next 5-min slot, watch countdownSec/endAt on the current slot, grab the next slot's slug while it's still PRE_OPEN, and start reading its book the moment tradable flips true.

Feel free to dm me to talk about this further Your detail payload's status: FUNDED and the orderbook's readiness are governed by different fields. FUNDED can be present even while a slot is not yet OPEN — so it tells you nothing about whether the book is readable. The book is gated purely by the slot's state == "OPEN" && tradable == true from the timeline endpoint. So: - Stop gating on status from get-market. It doesn't expose tradable. - Drive off GET /markets/timeline, take the slot whose state == "OPEN" and tradable == true, use that slot's slug for GET /markets/{slug}/orderbook. The doc text for the timeline slug field says this explicitly ("use it to fetch the orderbook… once tradable"). - For pre-warming the next 5-min slot, watch countdownSec/endAt on the current slot, grab the next slot's slug while it's still PRE_OPEN, and start reading its book the moment tradable flips true.

Thank you

Thank you