BTA / Delivery desk
A Trading Alert Webhook Payload Contract
Agree on identifiers, message meaning and validation before a transport success is mistaken for an accepted instruction.
Validate meaning as well as syntax
Valid JSON only establishes that an object can be parsed. It does not establish a recognised instrument, authorised action, current version or valid entry window. A receiver needs a documented message contract. Separate required fields from optional context, and describe what happens when a field is absent, unknown or inconsistent.
TradingView documents that valid JSON and plain-text messages use different content types. That mechanism is useful context, not a complete trading contract. Check the destination's actual requirements rather than assuming the example format on BTA will be accepted. Our synthetic messages are explicitly non-actionable and contain no real account credentials.
Preserve the original and received object
Retain the original payload, its version and the bytes or representation actually received. A template change, dropped field or truncated notification can change meaning while a delivery acknowledgement remains successful. Compare those objects directly. Redact secrets without deleting the identifiers and field structure needed to investigate the event.
A timestamp field must identify its source and event meaning. A family ID and version must state how amendments relate to originals. An instrument identifier should not rely on an ambiguous ticker alone. Where the actual vendor contract differs, preserve its semantics instead of mechanically substituting this publication's teaching fields.
Treat acceptance and execution separately
An endpoint accepting a request may only mean that the transport reached that endpoint. It may queue, validate or reject the application object later. A broker order adds a different authority and state machine. The review record should state which acknowledgement was obtained and which stage remains unobserved.
Use isolated, non-actionable samples to examine malformed objects, repeats and stale versions. A failed sample is valuable evidence about the declared boundary. Do not call a permissive parser reliable simply because every object receives a success response. The important question is whether the destination applies its documented contract without creating an unintended action.
Original Evidence Packet
| Artifact | Record to retain |
|---|---|
| Schema | Required fields, versions and permitted meanings |
| Payload pair | Original and received objects with safe redaction |
| Acknowledgement | Transport, application and account stages distinguished |
Continue the Investigation
Source Boundaries
Official references describe published mechanisms. BTA's evidence packets and proposed test procedures do not claim a completed paid-feed or account trial.