Broker API HubMenu

WebSocket close code

WebSocket close code: 1009 Message Too Big

As text you can copy

1009 Message Too Big
Kind
Close code
Where you meet it
When a WebSocket connection closes
Read from
RFC 6455, The WebSocket Protocol, section 7.4.1; the name is as the IANA WebSocket Close Code Number Registry writes it

What does 1009 Message Too Big mean in WebSocket?

An endpoint is ending the connection because it received a message that is too big for it to process.

Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.

Independent and unofficialrfc-editor.orgchecked

What it means in trading API work

Either you sent one very large message, for example a subscription to a great many instruments at once, or your own library closed the connection because an incoming message was larger than it allows.

This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.

What should I do about 1009 Message Too Big?

Split large subscriptions into smaller messages. If your own library sent the close, raise its maximum message size.

This page is an independent explanation in plain words. The definition itself is in the source it was read from, which is the authority if the two ever differ.