We are happy to announce beta release of MetaStats forex trading statistics API π.
Using MetaStats API you can develop applications similar to Myfxbook or MetriX extremely fast, saving time you otherwise spend for coding, optimizing and testing your own trading metrics calculation engine, since we already did it for you.
MetaStats is fast, cost-efficient and standards-driven, delivered to you as an easy to use REST API.
Documentation is published here: https://metaapi.cloud/docs/metastats/
You can test the API live via swagger UI here: https://metastats-api-v1.agiliumtrade.agiliumtrade.ai/swagger/#!/default/get_users_current_accounts_id_metrics
You are welcome to share your feedback, feature requests and bugreports via online chat.
Using MetaStats API you can develop applications similar to Myfxbook or MetriX extremely fast, saving time you otherwise spend for coding, optimizing and testing your own trading metrics calculation engine, since we already did it for you.
MetaStats is fast, cost-efficient and standards-driven, delivered to you as an easy to use REST API.
Documentation is published here: https://metaapi.cloud/docs/metastats/
You can test the API live via swagger UI here: https://metastats-api-v1.agiliumtrade.agiliumtrade.ai/swagger/#!/default/get_users_current_accounts_id_metrics
You are welcome to share your feedback, feature requests and bugreports via online chat.
Increasing API uptime was one of the most upvoted features requested by you. During last months we did a lot of job in this direction and happy to state that the 2-week average uptime per MT account connected to MetaApi have now exceeded 99.5% during trading session time. This is already a good result taking into account the specifics of MT platform. We will continue improving our API in order to keep it the best tool for forex app development.
We just released infrastructure with increased reliability for production workloads which deliver unmatched uptime level of up to 99.96% ππͺ.
Now, when you add an MT account to MetaApi you can choose one of the following reliability levels:
regular - this setting is intended for use with test applications. The expected uptime for MT accounts using regular reliability level is up to 99.5%
high - this setting is recommended for production applications overall and highly recommended for production applications using our CopyFactory copy trading API. The expected uptime for MT accounts using high reliability level is up to 99.96%
Please note that accounts with high reliability use more computational resources, so they are billed at increased rate. See https://metaapi.cloud/#pricing for more details.
All existing accounts use regular reliability by default and you can upgrade the reliability level via web UI.
Now, when you add an MT account to MetaApi you can choose one of the following reliability levels:
regular - this setting is intended for use with test applications. The expected uptime for MT accounts using regular reliability level is up to 99.5%
high - this setting is recommended for production applications overall and highly recommended for production applications using our CopyFactory copy trading API. The expected uptime for MT accounts using high reliability level is up to 99.96%
Please note that accounts with high reliability use more computational resources, so they are billed at increased rate. See https://metaapi.cloud/#pricing for more details.
All existing accounts use regular reliability by default and you can upgrade the reliability level via web UI.
metaapi.cloud
MetaApi - Powerful cloud forex trading API for MetaTrader
A professional cloud forex trading API for MetaTrader platform which includes MetaTrader REST API and MetaTrader websocket API and supports both MetaTrader MetaTrader 5 and MetaTrader 4. CopyFactory copy trading API included. Free usage tier available.
We've just released Python SDK 12.4.0 which contains client-side reliability improvements for large-scale applications and applications which should maintain connection with the server for a long time. This SDK version have passed our reliability tests successfully.
We recommend you to consider upgrading your apps to the new SDK version.
Similar updates for Javascript and Java will be released later in coming weeks.
We recommend you to consider upgrading your apps to the new SDK version.
Similar updates for Javascript and Java will be released later in coming weeks.
We've published detailed documentation about features available in our CopyFactory trade copying API. Please check https://metaapi.cloud/docs/copyfactory/ for more information if you are developing a trade copying app.
Today we released historical market data API π. Now in addition to streaming real-time quotes, candles, ticks and order books you can download historical candles and ticks. Note, that this feature is currently available for G1 infrastructure only. The feature is documented in https://metaapi.cloud/docs/client/restApi/api/retrieveMarketData/readHistoricalCandles/ and https://metaapi.cloud/docs/client/restApi/api/retrieveMarketData/readHistoricalTicks/.
Today we released historical market data API support and support for streaming real-time candles and ticks for MT4 G2 accounts π. MT4 G2 accounts provide access to a deeper market data compared to MT4 G1. So, enjoy a better and cheaper market data access for MT4 accounts!
We released a major update for CopyFactory API, CopyFactory 2 API π.
The updated version reduces trade copying latency so that trade copying happens almost instantly β‘ in the cloud, increases trade copying reliability πͺ and provides some bugfixes and improvements.
Some of the new features are scalping and HFT strategies support (due to decreased latency), automatic symbol mapping for forex, metals and crypto and ability to submit trading signals via REST API or SDK.
The new version is not fully backwards compatible, so that you will need to close your positions, stop CopyFactory 1 MT accounts, add MT accounts to CopyFactory 2 and configure trade copying in CopyFactory 2.
Please note that CopyFactory 2 is still in beta, so that it makes sense to test your trade copying setup before applying it to production.
We recommend you to start migration to the latest version of CopyFactory and SDKs as CopyFactory 1 will be disabled relatively soon in the future.
If you'll have any questions, issues or suggestions feel free to contact us via online chat.
The updated version reduces trade copying latency so that trade copying happens almost instantly β‘ in the cloud, increases trade copying reliability πͺ and provides some bugfixes and improvements.
Some of the new features are scalping and HFT strategies support (due to decreased latency), automatic symbol mapping for forex, metals and crypto and ability to submit trading signals via REST API or SDK.
The new version is not fully backwards compatible, so that you will need to close your positions, stop CopyFactory 1 MT accounts, add MT accounts to CopyFactory 2 and configure trade copying in CopyFactory 2.
Please note that CopyFactory 2 is still in beta, so that it makes sense to test your trade copying setup before applying it to production.
We recommend you to start migration to the latest version of CopyFactory and SDKs as CopyFactory 1 will be disabled relatively soon in the future.
If you'll have any questions, issues or suggestions feel free to contact us via online chat.
MetaStats SDK examples are now downloadable via web UI. Feel free to try out this feature.
CopyFactory 2 now supports closing positions when you remove a strategy, subscriber or a subscription. You can choose one of the following options: leave positions unmanaged, close them immediately or close them gracefully (continue copying close signals only). Feel free to try this feature in your applications.
We released a dashboard for CopyFactory 2 π which let you to use CopyFactory API just like a regular cloud trade copier, even if you have little or no coding skills.
Feel free to try this feature. You can submit your feedback via online chat.
The dashboard is quite minimalistic yet. We will be adding more features to it in coming weeks.
Feel free to try this feature. You can submit your feedback via online chat.
The dashboard is quite minimalistic yet. We will be adding more features to it in coming weeks.
We are considering to deploy MetaApi application in extra locations (regions) worldwide so that you can reduce network latency for brokers located far away from New York.
Please fill a short survey below so that we can plan our activities to appropriately fulfil your needs.
https://forms.gle/XHVRemcgjkxhbZsJ6
Please fill a short survey below so that we can plan our activities to appropriately fulfil your needs.
https://forms.gle/XHVRemcgjkxhbZsJ6
Google Docs
Extra MetaApi regions
At MetaApi we plan to launch extra regions for your applications to be able to trade and receive quotes and trade signals with lower network latency in case your broker is located far from New York. Over time we will be deploying our application in Londonβ¦
We released an update to MetaStats API to make margin, CAGR, MAR and pips metrics available π. In the new release you can also download trade history and open trades with duration, gain and pips metrics calculated for each trade.
We've just released an update in which we simplified the process of adding an MT account to MetaApi. π Now you can specify MT server name, account credentials and MetaApi will detect broker settings automatically. πͺ
If earlier you've failed to figure out how to configure provisioning profile properly and failed to add your MT account or faced weird behaviour (such as trades not being copied) as a result, we urge you to try out the new feature.
P.S. If you use API to create accounts in your app, please make sure you understand and implement the API contract fully, including error handling cases, since you still need to be able to follow the "older" process of creating an account using provisioning profile in case of broker settings detection error.
If earlier you've failed to figure out how to configure provisioning profile properly and failed to add your MT account or faced weird behaviour (such as trades not being copied) as a result, we urge you to try out the new feature.
P.S. If you use API to create accounts in your app, please make sure you understand and implement the API contract fully, including error handling cases, since you still need to be able to follow the "older" process of creating an account using provisioning profile in case of broker settings detection error.
Please support our project by "starring" it on github https://github.com/metaapi so that we can deliver exciting new features and improvements to you faster.
GitHub
metaapi - Overview
metaapi has 10 repositories available. Follow their code on GitHub.
We released server-side trailing stop loss support and improved a feature to specify SL, TP and pending order open price in relative units. π Hope you'll like the update.
Our monitoring suggests that capacity of our current vint-hill region will end soon. Thus we will be launching a new region in New York shortly. The new region will have less than 1ms ping time to brokers located in NY.
We will be upgrading regions support in python and javascript SDKs to make transition transparent for your apps. For these SDKs you will be able to connect to all regions at the same time via a single MetaApi class instance.
We will also release regions support for Java SDK shortly. In Java SDK you will need to create separate MetaApi class instance per region.
We will announce upcoming SDK releases in our telegram channel.
Please start updating your apps now to make sure the transition will not break your apps. It makes sense to migrate the apps to the current latest SDK version at this point and then upgrade SDK one more time once we will release the pending update for the SDKs.
If you'll have any questions, please contact us via online chat.
We will be upgrading regions support in python and javascript SDKs to make transition transparent for your apps. For these SDKs you will be able to connect to all regions at the same time via a single MetaApi class instance.
We will also release regions support for Java SDK shortly. In Java SDK you will need to create separate MetaApi class instance per region.
We will announce upcoming SDK releases in our telegram channel.
Please start updating your apps now to make sure the transition will not break your apps. It makes sense to migrate the apps to the current latest SDK version at this point and then upgrade SDK one more time once we will release the pending update for the SDKs.
If you'll have any questions, please contact us via online chat.
We just released an improved API for creating MT accounts π. Now you can create both live and demo MT accounts via convenient REST API and select account currency via accountType field.
We just released support for MT manager API to beta π.
MT manager API can be used to access and manage MT servers and intended for use by brokers and broker partners with manager access to an MT server.
The new API is a cloud REST API at this point. User (MT account) and balance management features are included into this release. Docs are published at http://metaapi.cloud/docs/manager/
The expected cost of the new API is $250/month and a trial period of 1 week is available.
Please contact us via online chat if you want to test or use the new API.
MT manager API can be used to access and manage MT servers and intended for use by brokers and broker partners with manager access to an MT server.
The new API is a cloud REST API at this point. User (MT account) and balance management features are included into this release. Docs are published at http://metaapi.cloud/docs/manager/
The expected cost of the new API is $250/month and a trial period of 1 week is available.
Please contact us via online chat if you want to test or use the new API.
As we informed you in one of the previous messages we are reaching capacity limit in our current vint-hill region.
Thus we've launched a new region in New York and will deploy new workloads in the new region by default soon.
Please make sure that your applications work correctly in situation when accounts are distributed across several regions.
- if you use javascript SDK, please upgrade to the latest SDK 18.0.0 and test your app with the new region as appropriate
- if you use python SDK it makes sense for you to wait until next major SDK release
- if you use REST API, please make sure your app can handle new region-specific API URLs and test your app with the new region as appropriate
- if you use Java SDK please upgrade to the latest SDK and test your app with the new region as appropriate
Feel free to contact us via online chat if you have any questions.
Thus we've launched a new region in New York and will deploy new workloads in the new region by default soon.
Please make sure that your applications work correctly in situation when accounts are distributed across several regions.
- if you use javascript SDK, please upgrade to the latest SDK 18.0.0 and test your app with the new region as appropriate
- if you use python SDK it makes sense for you to wait until next major SDK release
- if you use REST API, please make sure your app can handle new region-specific API URLs and test your app with the new region as appropriate
- if you use Java SDK please upgrade to the latest SDK and test your app with the new region as appropriate
Feel free to contact us via online chat if you have any questions.
