Skip to main content

HTTP errors

Structured thread state

A successful HTTP response can still contain a typed request for confirmation, approval, authentication, payment, completion, or cancellation. Render the thread event and operation state as returned. Do not convert message acceptance, a pending checkout, or a nonterminal status into generic success.

Support context

Record the operation, status code, latency, safe threadId, event ID, and Darwin response correlation ID. Never log API keys, OAuth tokens, provider credentials, payment data, or unredacted sensitive inputs.
Last modified on September 29, 2026