If your OKX bot's connection address still contains :8443, there's a deadline for changing it: October 31.
OKX's September 30 notice retires that port for WebSocket connections, which carry continuous market and account updates. Port 443 already works. The published change is simply to remove :8443, leaving the rest of the address alone. Both live and demo trading connections are affected.
I'd make the switch while both routes are available, rather than leave the first connection attempt until the old one closes. For anyone using a third-party bot, this is a specific question for its operator: has the OKX connection moved off 8443?
REST, the separate request-based interface many integrations use for orders, is unaffected. A bot using REST for orders and the old WebSocket address for updates needs the connection change even though its order interface isn't being retired.
Source: https://www.okx.com/en-eu/help/okx-websocket-port-8443-discontinuation-announcement
OKX's September 30 notice retires that port for WebSocket connections, which carry continuous market and account updates. Port 443 already works. The published change is simply to remove :8443, leaving the rest of the address alone. Both live and demo trading connections are affected.
I'd make the switch while both routes are available, rather than leave the first connection attempt until the old one closes. For anyone using a third-party bot, this is a specific question for its operator: has the OKX connection moved off 8443?
REST, the separate request-based interface many integrations use for orders, is unaffected. A bot using REST for orders and the old WebSocket address for updates needs the connection change even though its order interface isn't being retired.
Source: https://www.okx.com/en-eu/help/okx-websocket-port-8443-discontinuation-announcement