# Does FXCM still offer a REST API?

Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade.

This is the markdown version of https://openbrokerapi.com/guides/fxcm-rest-api, written from the same records as that page.

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.

We could not find a REST API listed by FXCM, and a third party guide dated June 2026 still sells one. This page sets out what we confirmed, what we could not, and what to do about the difference.

- Last reviewed: 2026-09-20

Unverified in part: carried over from an earlier version of this site. The links below are the sources it was written from, but its statements have not been re-read at source since the date shown, so check anything you rely on.

## What is confirmed

- FXCM’s own vendor repositories are still being pushed. [fxcm/ForexConnectAPI](https://github.com/fxcm/ForexConnectAPI), 193 stars, last pushed 10 Sep 2026.
- [fxcm/JavaAPI](https://github.com/fxcm/JavaAPI), 50 stars, last pushed 9 Jul 2026.
- Public repository creation around FXCM has all but stopped. Of 259 public repositories matching fxcm, 27 were created in the last 12 months, which is 10 per cent and the lowest recency share we measured in the latest reading.
- A third party guide dated June 2026 describes and sells an FXCM REST API.

Repository figures read 20 Sep 2026 from the api.github.com search endpoint. The full reading is on [the GitHub page](https://openbrokerapi.com/github).

## What is not confirmed

- Whether FXCM offers a REST API to retail clients today. We did not find one listed by FXCM.
- Whether the API the third party guide sells is a current FXCM product, a legacy one, or something else carrying the name.
- Nothing on this page was tested. We hold no FXCM account and we called no FXCM endpoint, so this is a reading of published material and not a test of an API.

ForexConnect is not REST. A maintained repository tells you the vendor is still shipping code for that product. It tells you nothing about whether a REST product exists, is open to new clients, or is documented.

## What to do

- Ask FXCM in writing what API access it offers today, and to which account types, before you write any code against a third party description of it.
- Treat a third party guide that post dates the vendor’s own silence as unconfirmed, however recent its date is, and whatever it charges.
- If the answer comes back as ForexConnect rather than REST, the two repositories above are where the maintained code is.
- If you get a written answer from FXCM, send it to us and we will publish it with its date.

## Where to go next

- [FXCM API facts, with the date each one was checked](https://openbrokerapi.com/brokers/fxcm)
- [The GitHub reading these repository figures come from](https://openbrokerapi.com/github)
- The demand evidence behind the ranking
- [Corrections and right of reply](https://openbrokerapi.com/corrections)

## More on the FXCM API

- [FXCM API page](https://openbrokerapi.com/brokers/fxcm): The full record: access, authentication, limits and the source for each.

## Licence and how to cite

The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page.

Cite as: Does FXCM still offer a REST API?. Broker API Hub, https://openbrokerapi.com/guides/fxcm-rest-api, newest check 2026-09-20.

Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.