Gold trading basics · Lesson 42 of 54

Gold Signal Webhooks: Verify Delivery, Freshness and Duplicates

Separate a generated gold signal from a delivered event, a displayed card and a filled order.

Delivery Is Not Execution: instructional diagram for lesson 42 — CYGURU GOLD · Original lesson schematic. Examples are illustrative.

A signal travels through several stages

A script may generate an event, an alert service may attempt delivery, a receiver may accept it and a website may display it. Each stage needs its own evidence. A visible chart label proves none of the later stages by itself. For a public signal dashboard, preserve event time and receipt time so a delayed message is not presented as a fresh market condition.

Give each event a stable identity

A teaching payload might include rule version, stream identifier, full symbol, timeframe, bar time, event type and a stable event ID. The receiver can use that ID to recognize a repeated delivery. The exact identity design depends on whether a rule permits multiple events per bar. Do not use the display text alone as a unique key when two legitimate events can share the same words.

Trace a timing and duplicate example

Suppose an event is generated at 10:00:00 UTC and received at 10:00:04. The observed transport delay is four seconds; it is not an execution delay or a fill guarantee. If a retry arrives at 10:00:09 with the same event ID, a dashboard can record the second delivery while retaining one signal card. A genuinely new event must have its own identity under the documented scheme.

Validate the receiver’s behavior

Use HTTPS, a documented authentication method and strict payload validation. Do not send account passwords or trading credentials in alert bodies. Treat unknown fields, malformed values, mismatched versions and stale event times according to an explicit policy. Platforms can retry some failures, and delivery can fail. Durable acceptance, processing and public display should be distinguishable in logs rather than hidden behind a single success label.

Practice task: test three paper messages

Prepare one valid event, one duplicate of that event and one malformed or stale event. In a non-trading test receiver, verify the accepted count, duplicate record and rejection explanation. Compare the alert delivery log with the receiving log and displayed timestamp. No order should be inferred from successful delivery: actual broker execution requires a separate authorized system and a fill record.

Gold Signal Webhooks: Verify Delivery, Freshness and Duplicates

A signal travels through several stages

Give each event a stable identity

Trace a timing and duplicate example

Validate the receiver’s behavior

Practice task: test three paper messages

Can you apply the idea?

Make this lesson part of your process.

Gold Trading Mastery

Continue the beginner course

Lesson sources and further study

Core course references

Connected reading