Use case · EA developers
For EA developers: read-only SDK & licensing.
A read-only MQL SDK lets any Expert Advisor or indicator emit a log or alarm in one line and POST it to a signed webhook you control. Selling an EA? License it through Chartping — issue, meter and revoke keys via an API. It never trades.
The SDK
Alerting for your EA, in one line.
One line to log or alarm
Any MQL EA or indicator emits a log line or an alarm with a single call to the read-only Chartping SDK. It never sends an order — it reports.
Signed webhooks to your backend
Any alarm can POST to a URL you control — a Discord, Telegram or Slack incoming webhook, or your own backend — signed with HMAC-SHA256 (an X-Chartping-Signature header) and retried on failure.
“Powered by Chartping”
Give your users push, SMS, voice and webhook alerts on the risk rules they set, without building an alerting stack yourself.
Licensing platform
Sell and protect your EA.
Issue, meter and revoke licenses for your own Expert Advisor — the licensing plumbing, handled.
Issue & redeem keys
Mint redeemable license keys for your EA and hand them to customers.
Meter usage
Track activations and usage per license through the API.
Revoke instantly
Kill a license the moment it’s misused — the change propagates to the EA.
Lifecycle webhooks
Get HMAC-signed license lifecycle events (issued, redeemed, revoked) to your backend.
Before you build: the SDK is free, the licensing rail is not the same thing. You can compile the MQL SDK into your EA and sell that under your own name at no cost to you — the terms are the Chartping MQL SDK Licence shipped with it. Issuing licence keys to your customers is the separately billed part: 5 licensed traders free, then tiers up to unlimited whose prices are not published yet. Tell us what you expect to need and we will tell you where we land before you commit to anything.
And one hard precondition. Issuing licences means we process your customers' personal data on your instructions — you are the controller, we are your processor. You must accept the Data Processing Agreement (full text) before the licensing API will answer you at all. The product enforces it; it does not ask.
See everything Chartping watches or which tier includes what.
Message queues & routing
Move a signal from anywhere to anywhere.
A read-only routing layer for developers and desks: publish to a durable queue, subscribe from any language, and fan out to webhooks, chat or a subscribed terminal. Chartping is the wire — it never trades.
Publish with a key
Push alarms or copy-trade signals to a durable queue with a publish key — from TradingView, a script, your EA or your own backend.
Subscribe in any language
Read with a separate subscribe key over long-poll, SSE or WebSocket. No SDK required — any HTTP client works.
Fan out to sinks
Route a queue to webhooks and chat (Discord, Telegram, Slack) or straight back to an EA on a subscribed terminal.
Scoped, revocable keys
Publish and subscribe are separate capabilities, each revocable on its own — a leaked read key can never write.
Developer FAQ
Do you give investment advice or signals?+
No. Chartping only watches the rules you define and notifies you. It does not suggest strategies, values or trades.
Is there a developer SDK — can it alert my own backend?+
Yes. A read-only SDK lets any MQL EA or indicator emit a log or alarm in one line, and any alarm can POST to a webhook URL you control, signed with HMAC-SHA256. EA vendors can also license their products through Chartping — issue, meter and revoke licenses with an API. It never trades.
Build alerting into your EA.
Join the waitlist — be among the first to know what's happening across every account you trade.