OKX WebSocket Port 8443 Ends October 31: Fix Your Bot
Short answer: OKX stops accepting WebSocket connections on port 8443 on October 31, 2026 for the public internet. Colo connections follow on November 16. The fix is to delete :8443 from your WebSocket URLs. The host and path stay the same. REST calls are not affected. A separate ELP-to-RPI rename also hits its deadline on October 31.
If your OKX trading bot, price feed or dashboard connects to a URL with :8443 in it, it has thirteen days left.
The change is tiny, one port number, which is exactly why it gets missed. Nothing breaks until the day it does.
Not financial advice. Dates and URLs come from the OKX API changelog (docs-v5), last updated October 16, 2026, which I read on October 18, 2026. OKX can revise the changelog, so recheck it before you deploy.
Contents
- When does OKX stop port 8443?
- Which WebSocket URLs need to change?
- How do you find the old port in your code?
- Is the REST API affected?
- What is the ELP to RPI rename?
- What Trips People Up
When does OKX stop port 8443?
According to the OKX API changelog updated on October 16, 2026, OKX will stop accepting WebSocket connections on port 8443 on October 31, 2026 for the public internet and on November 16, 2026 for Colo connections.
| Connection type | Port 8443 stops | Days from Oct 18, 2026 |
|---|---|---|
| Public internet | October 31, 2026 | 13 |
| Colo | November 16, 2026 | 29 |
The changelog states the required action in four words: remove :8443 from your WebSocket URLs.
Which WebSocket URLs need to change?
On OKX’s Global site, the production and demo-trading WebSocket URLs keep the same host and path and only lose the :8443 port, so wss://ws.okx.com:8443/ws/v5/public becomes wss://ws.okx.com/ws/v5/public.
| Environment | Old URL | New URL |
|---|---|---|
| Production, public | wss://ws.okx.com:8443/ws/v5/public | wss://ws.okx.com/ws/v5/public |
| Demo trading, public | wss://wspap.okx.com:8443/ws/v5/public | wss://wspap.okx.com/ws/v5/public |
The same removal applies to the other affected paths the changelog lists: /ws/v5/private, /ws/v5/business and /ws/v5/public-sbe.
How do you find the old port in your code?
To find every OKX WebSocket URL that still uses port 8443, search your repositories, config files and environment variables for the string :8443 and for the hostnames ws.okx.com and wspap.okx.com.
A plain text search is enough:
grep -rn ":8443" .
grep -rn "okx.com" .Check places a code search will not reach. Third-party trading libraries sometimes hard-code endpoints, so look at the version you have installed and its release notes. Deployed containers, cron jobs and cloud functions often carry an old copy of the config. Hosted bot platforms keep the URL in a settings page, not in your code.
When I checked the changelog entry, I found that it covers Colo connections as well as the public ones. If you run from a Colo setup, you have until November 16, not October 31, but I would not wait for the later date.
Is the REST API affected?
No. The OKX changelog says the port 8443 change applies to WebSocket connections only, and REST API calls are not affected.
That is worth knowing if your bot places orders over REST and only reads prices over WebSocket. The orders keep working while the feed goes quiet, which is the worst combination. A bot that trades on stale data is more dangerous than one that stops.
What is the ELP to RPI rename?
OKX is renaming its Enhanced Liquidity Program (ELP) to Retail Price Improvement (RPI), and the old ELP names stop being accepted after the deprecation deadline of October 31, 2026, according to a changelog entry dated July 28, 2026.
| Old name | New name |
|---|---|
| isElpTakerAccess | rpiTakerAccess |
| elp | rpi |
| elpMaker | rpiMaker |
| ordType: elp | ordType: rpi |
| books-elp | books-rpi |
Both names are accepted until the deadline, and if you send both the RPI name wins. The new books-rpi order book is available as a WebSocket public channel and at GET /api/v5/market/books-rpi, and it supersedes books-elp. If your bot never touches ELP fields, ignore this section.
What Trips People Up
The failure is quiet. A script that reconnects in a loop may look busy in your logs while receiving nothing useful, so add an alert for ‘no market data for N seconds’.
Test the new URL in demo trading first. The demo host wspap.okx.com changes the same way, so you can validate the fix without touching a live key.
Tips
- Change the URL in a config variable, not in five places in the code.
- Deploy the fix at least a week before October 31 so a bad release leaves time to roll back.
- Subscribe to the OKX API changelog or announcements so the next deprecation is not a surprise.
Warnings
- Do not paste API keys into a forum or chat to get help debugging a connection. Use a read-only key if you must share logs.
- Never download a ‘fixed’ OKX bot from a link in a message. Update your own code or a library from its official repository.
- Dates and field names can change. The changelog, not this article, is the authority.
FAQ
What happens to my OKX bot after October 31, 2026 if I do nothing?
Its WebSocket connection to port 8443 on the public internet will no longer be accepted, so any price or order feed that depends on it stops. REST calls are not affected.
Do I have to change the host or path of the OKX WebSocket URL?
No. The changelog says only the port changes. The host (ws.okx.com or wspap.okx.com) and the path (for example /ws/v5/public) stay the same.
Does the October 31 deadline also apply to the demo trading WebSocket?
Yes. The changelog lists the demo URL wspap.okx.com:8443 among the affected addresses, and the replacement is the same address without the port.
Sources
- OKX API v5 changelog (port 8443 entry updated October 16, 2026; ELP to RPI entry dated July 28, 2026)
- OKX API v5 documentation
🔗 Related guides
Fact-checked against the OKX API v5 changelog as read on October 18, 2026. Not financial or investment advice.
