---
title: "Serverless, edge, and observability"
description: "<p>Operate HTTP clients, webhooks, traces, and queues in bounded runtimes.</p>\n<h2>How it works</h2>\n<p>Operate HTTP clients, webhooks, traces, and queues in bounded runtimes."
---

> Documentation Index
> Fetch the complete documentation index at: https://tidymessages.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Serverless, edge, and observability

<p>Operate HTTP clients, webhooks, traces, and queues in bounded runtimes.</p>
<h2>How it works</h2>
<p>Operate HTTP clients, webhooks, traces, and queues in bounded runtimes. TidyMessages keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.</p>
<h2>Set it up</h2>
<ol>
<li>Choose the sending identity, conversation, channel, and environment.</li>
<li>Check capability, consent, current state, and channel policy.</li>
<li>Use an idempotent request and verify the resulting event history.</li>
</ol>
<h2>What to expect</h2>
<ul>
<li>The operation is traceable by stable request and resource identifiers.</li>
<li>Acceptance, provider delivery, and customer interaction remain separate states.</li>
<li>Retries and reordered events do not duplicate the customer action.</li>
</ul>
<blockquote>
<p>[!TIP] Keep API keys, signing secrets, customer addresses, and message bodies out of source and logs.</p>
</blockquote>

Source: https://tidymessages.helpcent.re/sdks-integrations/serverless-edge-and-observability/index.mdx
