Menu

Same Order Book, Five Depth Caps — and One Venue That Quietly Answers 100
📰

Same Order Book, Five Depth Caps — and One Venue That Quietly Answers 100

DEV Community: api·HMwork·10 days ago
#tjhiY66m
#devtoapi#devto#dev#ad#depth
Reading 0:00
15s threshold

Same Order Book, Five Depth Caps — and One Venue That Quietly Answers 100

How deep can you ask the L2 order book to go? We put the same question to five exchange APIs on 6 November 2026 and got five different answers — and one venue that ignores an out-of-range parameter without a word of warning.

Disclosure: Produced with AI assistance from data pulled directly from official exchange APIs and documentation. No sponsored placements at the time of writing; if that changes, an #ad notice will appear where any affiliate link is used. Nothing here is financial advice — a technical write-up about API behavior.

Why depth caps matter

If you build anything that touches market data, you will call an order book endpoint. Almost every venue exposes one with a size parameter, and most developers assume it works the same way everywhere: ask for N levels, get N levels, get an error if N is too big.

That assumption is wrong in an interesting way.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.