Skip to main content

HTTP errors

Structured Action states

A successful HTTP response can still require user input, connection, payment, approval, or more authority. Render the supplied status, actionRequired, and availableActions; do not convert them into a generic error or success message.

Support context

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