Every StaxInvesting article tagged api security · 4 posts.
4 articles
Three of the four sources of duplicate trade signals are self-inflicted. Idempotency is not primarily an attack defence — it is protection against your own infrastructure behaving normally, in the one place where a repeated request costs money immediately.
A webhook endpoint that places orders is an unauthenticated URL that spends money. Since cryptographic verification is not available, protection has to be layered: constant-time secret checks, idempotency keys, timestamp windows, and hard server-side limits on what any payload can do.
TradingView imposes no payload schema — the format is entirely yours to design. What it does control is the transport: one attempt, no retry, a three-second timeout, and no request signing. Both facts shape what a sane payload looks like.
Scoping a broker credential correctly bounds what an attacker can do with it. The 3Commas breaches proved it does not make one safe: accounts were drained using trade permissions alone, through the market rather than through a transfer.
