What should happen after a webhook receiver returns HTTP 200?

What this means in practice

HTTP 200 should mean the receiver accepted the HTTP/application request, not that the broker guaranteed a fill. Track execution as a separate state after acknowledgement. This page is specifically about “What should happen after a webhook receiver returns HTTP 200?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — 200 then broker rejects

HTTP 200 describes the receiver's acceptance contract, not the final broker outcome. Preserve a separate execution state so later cTrader success, rejection or duplicate suppression is visible without changing the transport record. For Scenario A — 200 then broker rejects on question 35, use that evidence specifically to answer “What should happen after a webhook receiver returns HTTP 200?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — 200 then async success

HTTP 200 describes the receiver's acceptance contract, not the final broker outcome. Preserve a separate execution state so later cTrader success, rejection or duplicate suppression is visible without changing the transport record. For Scenario B — 200 then async success on question 35, use that evidence specifically to answer “What should happen after a webhook receiver returns HTTP 200?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — 200 for known duplicate

HTTP 200 describes the receiver's acceptance contract, not the final broker outcome. Preserve a separate execution state so later cTrader success, rejection or duplicate suppression is visible without changing the transport record. For Scenario C — 200 for known duplicate on question 35, use that evidence specifically to answer “What should happen after a webhook receiver returns HTTP 200?”; keep it separate from the evidence for the other scenarios on this page.

What to check

• TradingView alert log and exact send time
• HTTP status and receiver timestamp
• validated payload plus signal ID
• cTrader result only after transport is proven

Practical rule

For “What should happen after a webhook receiver returns HTTP 200?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.