Troubleshooting
Symptom-first answers for the failures you are most likely to hit while integrating.
Most surprises on this API come from three places: a 202 is not a delivery
confirmation, the stream is lossy by design, and idempotency does not apply to
every command. Find your symptom below.
Still stuck
Two things are worth checking before you go deeper. Confirm the command
actually settled — an unsettled commandId and a failed one call for very
different responses. And confirm your host supports the operation at all: there
is no capability discovery endpoint, so an operation that works in one account
and fails with capability_not_negotiated in another is a fleet difference,
not a bug in your code. See Capabilities.