Pocket Option API and websocket access: what actually exists
Pocket Option publishes no API and no developer documentation. There is no REST endpoint, no API key issuance and no websocket specification on any page of pocketoption.com. What exists instead is third-party code.
18+. Unofficial clients have no status in the company's agreement, and trading can cost the entire amount you deposit. Risk notice.
A GitHub search for «pocketoption» returned 215 repositories on 29 August 2026, led by ChipaDevTeam/PocketOptionAPI at 150 stars, with Mastaaa1987/PocketOptionAPI-v2 and chema-creator/PocketOptionApi describing themselves in their own words as «unofficial». They work by talking to the same websocket the browser terminal uses. The agreement, meanwhile, prohibits profiting through «operations not instructed by the Company» and «vulnerabilities in the Company's official website(s)», and lets the company reset trading results. This page names the code; it links to none of it.
01 · Documentation
There is no public Pocket Option API
On 29 August 2026 we read every public layer of pocketoption.com looking for an API reference, an endpoint list, key issuance or a websocket specification. There is none.
The documents section — Terms and Conditions, AML and KYC policy, Privacy policy, Payment policy, Information disclosure — has none either, and Quick start covers only registration, verification and deposit.
PUBLIC OFFER · DEFINITIONSThe company provides
a specially prepared web interface (Trading Terminal)to carry out trading operations within the Client's Area.The only interface the agreement describes. Keys and endpoints are never mentioned.
For «pocket option api documentation» the consequence is simple: the document does not exist, and any page presenting itself as official Pocket Option API documentation is not published by the platform. The supported way in is the Pocket Option web terminal and the official clients built around it.
Repository names are given as text only. We do not link to third-party code.
02 · Third-party code
What the websocket libraries actually are
Search for «pocket option websocket api» and you land on code repositories, not on the platform. A GitHub search for «pocketoption» in names and descriptions returned 215 repositories on 29 August 2026. The largest:
Technically they do the same thing: they connect from a script to the websocket channel the browser terminal uses and parse its messages. Hence feature lists that mirror the terminal: reconnection, demo and real accounts, assets with payouts.
The authors write «unofficial» for a reason: the channel has no specification and can change without warning. Even the most-starred repository is somebody else's code, not a Pocket Option API.
03 · The agreement
What the agreement says about unauthorised access
The public offer never mentions an API, but its clauses cover what an unofficial client does.
PUBLIC OFFER · PROHIBITED ACTIVITYAny activity aimed at profit
using operations not instructed by the Company, vulnerabilities in the Company's official website(s), bonus speculation, and abusive tradingis prohibited.Remedy: termination or cancellation of trading results.
Next to it, the company may forbid copying other traders' operations and reset copied results. And a client is prohibited to have more than one Trading Account
, so a separate account for experiments is not an option either.
The practical reading, without advice either way: an unofficial client has no status in the agreement, and whether its use counts as an operation not instructed by the Company
is decided by one party, the company.
The company may end the agreement over prohibited activity.
Trading results obtained that way can be cancelled.
Copying other traders can be forbidden and copied results reset.
A second profile is itself grounds to terminate.
04 · Built in
The automation the platform does offer
What the platform names on its own pages is a short list of interface features. None of them is an API. The terminal follows the market sessions, and OTC instruments, quoted by the platform itself, keep running when regular markets close.
TELEGRAMTelegram bot
One of four official channels in the footer. A way to reach the account, not a developer interface.
WEB APPWeb App
The browser terminal itself, and the route on iPhone: no iOS app is linked.
SOCIALSocial Trading
A section of the platform's site, presented as an interface feature. We give no performance figures.
TERMINAL TOOLSIndicators and Signals
Listed beside «Technical Analysis Tools» as the terminal's built-in kit: tools on the chart, not a feed a program can connect to.
The chart above is the part of the terminal unofficial libraries read from the websocket channel and rebuild in a script. Even a built-in feature carries a caveat: the company may forbid copying other traders' operations and reset copied results. What the platform does publish openly is its payout percentages, asset by asset, in the assets and payout table.
05 · FAQ
Questions about the API
Is there official Pocket Option API documentation?
No. Nothing resembling an API reference, endpoint list, key issuance flow or websocket specification appears anywhere on pocketoption.com, including its documents section. Any page presenting itself as official Pocket Option API documentation is not published by the platform.
What are the PocketOption API repositories on GitHub?
Third-party code. A search for «pocketoption» returned 215 repositories on 29 August 2026, led by ChipaDevTeam/PocketOptionAPI with 150 stars. Mastaaa1987/PocketOptionAPI-v2 calls itself an «Unofficial API for PocketOption platform» and chema-creator/PocketOptionApi an «Unofficial Python WebSocket client» — the wording is the authors' own.
How does a websocket client for Pocket Option work?
It connects to the same websocket channel the browser terminal uses and parses its messages, which is why such projects list features like auto-reconnect, demo/real routing and asset catalogue with payouts. Because the channel is undocumented, its behaviour can change at any time without notice.
Does using an unofficial client break the terms?
The agreement gives the company broad grounds against it. It prohibits profiting through «operations not instructed by the Company» and «vulnerabilities in the Company's official website(s)», and allows termination or a reset of trading results. It separately allows the company to forbid copying other traders' operations and reset copied results.
Verdict
The API question, in one screen
WHAT EXISTS
- Four official clients: Android, APK, Web App, Telegram
- 215 third-party repositories, the largest at 150 stars
- An undocumented websocket channel behind the terminal
WHAT DOES NOT
- No REST API, endpoint list or API keys
- No developer documentation
- No contract status for unofficial clients
Official API: none. Unofficial clients: plenty, open and named above, with no standing in the agreement. For a developer that means building on a channel that can change overnight; for a trader, results the company may reset. The other missing piece people search for, a MetaTrader client, is covered in the MT4 question.