Tickwire docs
Read, stream and trade MetaTrader 4 and 5 accounts over one API, with a health check for each account.
Tickwire runs one real MetaTrader terminal per trading account and puts an API in front of it. MT4 and MT5 accounts look the same from the outside.
Start here
- Quickstart: your first order in under two minutes in the free sandbox, then the same calls on your broker account.
- Authentication: the header forms we accept and how to scope tokens.
- Health: what
healthy,stale,disconnectedanddownmean, and how we measure them.
Three ways to call Tickwire
| Surface | Paths | Use it when |
|---|---|---|
/users/current REST API | /users/current/accounts/…, socket.io streaming | Your code already calls this API style or you want its field names |
/v1 and terminal routes | /v1/…, /mt4/{id}/…, /mt5/{id}/… | You’re moving an integration that uses these routes |
| Tickwire extras | /users/current/accounts/{id}/health, /audit, /ws, webhooks | You want per-account health, the audit log or plain WebSocket streaming |
All three surfaces reach the same terminals, so you can mix them. The native /v1 lists are
cursor-paginated; the other surfaces keep their existing list shapes.
By use case
- Prop risk tool: watch equity and flatten on breach.
- Trade copier: copy orders to many accounts, with idempotency keys so a retry never fills twice.
- Trading journal: read-only history sync.
- Trading bot: stream prices and trade.
- Example projects: quickstarts, webhook receivers, a pre-trade guard and MCP setup to copy. Sandbox only.
Early access
Tickwire is in early access. Pages about features that aren’t available yet say so at the top.