出典確認済みリサーチ: Order Preview Validate Amend

Decision outcome: For any bot or API workflow, log the client order ID, dry-run or preview result, exchange acknowledgement, final order status, WebSocket reconciliation, cancel or amend result and retry idempotency policy separately. Stop if an accepted request is being treated as a fill, a validation response is treated as a live order, or a lost response can duplicate an order.

Evidence snapshot. This article was researched at 2026-09-26T20:44:49.316Z using Coinbase Developer Platform, Kraken Support, OKX, Binance Developer Docs. A local queue, old draft, search snippet, social repost, price chart or AI summary was not treated as proof. Those surfaces can suggest a question, but every material claim below is tied to the cited source list and claim map.

Verified facts. Claim c1: Coinbase Developer Platform describes Advanced Trade API as supporting programmatic trading and order management through REST API and WebSocket protocol. Claim c2: Kraken says the validate input parameter for REST AddOrder or WebSocket addOrder simulates order checks and a validate call never returns an order ID. Claim c3: OKX documentation says a successful order-amend response means the request was accepted and users should refer to WebSocket order results for the amendment outcome. Claim c4: Binance Developer Docs present Spot REST API endpoint definitions, request parameters, payload schemas, endpoint security types and rate-limit information for authenticated trading workflows. These facts are intentionally narrow. They do not prove account eligibility, future availability, execution quality, legal status beyond the cited wording, tax treatment, account approval, support outcome, redemption success, price direction, liquidity depth or platform solvency.

Decision discipline for order preview validate amend acknowledgement API execution controls radar. The useful answer is not a universal winner. It is a source-bound scorecard: which official source answers the immediate question, which control is blank, which blank changes user risk, which test is reversible and which condition reopens the decision. An honest blank is safer than an invented advantage.

FAQ. What is the short answer? Exchange API order-control words are not interchangeable. What should be verified first? Verify the official source and the exact control surface. What should not be inferred? Do not infer eligibility, future support, legal treatment, tax treatment, recovery, execution quality, liquidity, redemption, consumer protection or account approval. When should the user stop? Stop when source, object, user state, permission, route, issuer, jurisdiction or failure handling is unclear.