---
title: "Idempotency"
description: "<p>Reuse the same key for uncertain writes and never reuse it for different input.</p>\n<h2 id=\"how-it-works\">How it works</h2>\n<p>Reuse the same key for uncertain writes and never reuse it for different input."
---

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

# Idempotency

<p>Reuse the same key for uncertain writes and never reuse it for different input.</p>
<h2 id="how-it-works">How it works</h2>
<p>Reuse the same key for uncertain writes and never reuse it for different input. Messages.org keeps channel-specific behavior explicit while providing stable identifiers, safe retries, and auditable lifecycle events.</p>
<h2 id="set-it-up">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 id="what-to-expect">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://help.messages.org/platform/idempotency/index.mdx