Create or update the duplicate-message suppression policy
Upserts the organization’s single duplicate-message suppression policy. When a matching policy fires, an identical message body to the same recipient on the same channel is silently suppressed within window_seconds — the guard against two campaigns sending the same promo back-to-back. Omit channels (or pass null) to cover every outbound messaging channel, and omit applies_to_categories to cover every message category; restrict the category list to marketing copy so OTP and transactional resends are never suppressed. Body: window_seconds (3600–7776000), optional enabled (defaults true), and optional channels / applies_to_categories (null or omitted = every channel / every category). Requires owner, admin, or developer role.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false