Broker API capability tables
16 capabilities read across 21 broker records and 8 platform API records. Each cell says yes, no, partial or not recorded, and links to the row that shows its source.
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.
Not recorded means this site holds no record. It does not mean the broker or platform lacks the capability. Rows are in name order, the order is not a ranking, and nothing here recommends a broker.
What the four states mean
- Yes
- A record on this site says so: a structured field, a record that exists, or a sentence in a record that was read and entered in the capability facts register, with the reason printed beside it. 236 of the 448 cells on this page.
- Partial
- A sentence in a record gives part of it: one route and not another, or a demo of the platform and not of the API. The reading is a row of the capability facts register, and the reason and the scope are printed beside it. 17 of the 448 cells on this page.
- No
- A record on this site says no: a structured field set to false, or a sentence in a record that says so, read and entered in the capability facts register. 18 of the 448 cells on this page.
- Not recorded
- This site holds no yes or no for it. That is a gap in this dataset. It is not a statement that the broker or platform lacks the capability. 177 of the 448 cells on this page.
No cell is decided by a program reading meaning into a sentence. A state comes from a structured field in a record, from a record existing, or from the capability facts register: 80 cells where a person read the record's own sentence and entered yes, partial or no because its words settle it. Each of those prints the reason and the scope beside the sentence itself, and takes its status, source and checked date from that sentence, so a reading of an unverified sentence is unverified. When a sentence changes after it was read, the site cannot be published again until someone has read the new wording. Where a sentence settles nothing, the cell stays at not recorded and the capability's page prints the sentence with its source.
23 cells rest on a record that is labelled unverified. Each of those carries the word unverified under its state.
Brokers
Platform APIs
A platform record is itself an API, so these columns are kept for brokers only and are left out here: Own API, Platform APIs reachable.
The capabilities
Each has a page of its own, with one row per record, the words that support the state, the source and the date it was checked.
- Own API
- Some brokers publish an API of their own, so your code talks to the broker's servers directly. Others publish none, and an account there can only be automated through a platform API.
- Documentation link
- The provider's own documentation is the page to trust when anything else disagrees with it, this site included. A link to it is the first thing to look for before you write code.
- Demo or sandbox
- A demo or sandbox account trades virtual money, so a mistake in your code costs nothing there. Whether the API works on the demo at all, and on what terms, differs from one provider to the next.
- Streaming
- Streaming pushes each price or account update to you over a connection that stays open, so a program does not have to ask again and again. Providers do it over different protocols.
- Authentication described
- Authentication is how an API knows a request is yours: a key or token sent with every request, a login call that returns a session token, or OAuth. You need to know which before you can make a first call.
- Published rate limits
- A rate limit is the number of requests an API accepts in a period before it refuses more. A published limit lets you pace a program before it is refused, instead of finding the ceiling by hitting it.
- Official SDK or library
- An SDK or client library wraps an API so you call functions instead of building each request by hand. An official one is published by the provider itself, as opposed to one written by the community.
- Python library
- A Python library lets you call an API from Python without writing the HTTP requests yourself. Python is the language most people learn first for this kind of work.
- Official MCP server
- An MCP server lets an AI assistant use an API through a standard set of tools. An official one is published by the broker or platform itself. An assistant with order tools can place real trades, so read what a server can do before you connect one.
- Community MCP server
- A community MCP server is written by someone other than the broker or platform. It is not the provider's product, so read its code before you give it a key, and start with a demo account.
- Platform APIs reachable
- A platform API belongs to a trading platform rather than to a broker. Where a broker offers such a platform, an account there can be automated through the platform even if the broker publishes no API of its own.
- Endpoints documented here
- An endpoint is one address in an API that does one job, such as listing positions or placing an order. An endpoint page on this site gives the method, the path, the parameters and the source they were read on.
- Error codes decoded here
- An error code is what an API sends back when it refuses a request. A decoded error page on this site gives what the code means, the usual cause and the source it was read on.
- OpenAPI file here
- An OpenAPI file describes an API in a form that tools can read, so you can generate a client or load it into an API explorer. The files on this site are unofficial descriptions generated here from the endpoint records, not files issued by a broker.
- Quickstart here
- A quickstart walks from getting access to making a first call, one step at a time. It is the shortest route to finding out whether an API will do what you need.
- Dated changes recorded
- APIs change: endpoints are added, retired or altered, and limits move. A dated change record says what changed, when, and the page it was read on.
Download the grid
Every cell, with its state, supporting words, source and checked date, as JSON or CSV. Licensed CC BY 4.0. See the other downloads for how to cite.
Where to go next
How to cite this
Broker API capability tables. Broker API Hub, https://openbrokerapi.com/capabilities, newest check .
Where you rely on a single figure, cite the source and the checked date printed beside it as well.