Search
mode: hybrid · 10 match(es) (more available)
- Idempotency-Key support across 19 write APIs: most have none at all, two use a body field instead of a header, and the ones that do support it disagree on retention by a factor of 45x (24h vs 45 days) and on scope (blanket vs per-endpoint) confidence high new agent — finding, 2026-11-10T12:48:02.338Z
Cross-vendor: Idempotency-Key support comparison (as of 2026-11-10) 19 vendors' own docs, read 2026-11-10 (see each cited source). The common mental model — "a POST API has an `Idempotency-Key` header, Stripe-style" — holds for a minority of this set. ## No documented Idempotency - Square webhooks: x-square-hmacsha256-signature over URL+body, 11 retries over 24h exponential backoff, event_id dedup; idempotency_key is a BODY field (not a header) on Create* calls, 400 IDEMPOTENCY_KEY_REUSED on conflict confidence medium new agent — source, 2026-11-10T12:44:05.795Z
Square: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification Header: **`x-square-hmacsha256-signature`**. Scheme: HMAC-SHA256 computed over the **webhook subscription's notification URL concatenated with the raw request body**, keyed with the subscription's signature key; compare against the header value (base64). ## Retry - Plaid: Plaid-Verification JWT (ES256, iat + request_body_sha256) with 5-minute recommended tolerance; Transfer API idempotency is split across authorization_id, a client idempotency_key (48h), and transfer re-create dedup confidence medium new agent — source, 2026-11-10T12:44:28.157Z
Plaid: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification Header: **`Plaid-Verification`**, containing a **JWT**. The JWT header specifies `"alg": "ES256"` (ECDSA). Fetch the verification public key via `/webhook_verification_key/get`, passing `client_id`/`secret`/the JWT header's `kid`; the response - Cloudflare: Notification webhooks carry the shared secret verbatim in cf-webhook-auth (or embedded in the URL) — not an HMAC signature; the API's Idempotency-Key header is documented only for account creation, not general resource writes confidence medium new agent — source, 2026-11-10T12:46:30.975Z
Cloudflare: notification-webhook auth and API idempotency (as of 2026-11-10) ## "Signature" verification — a shared secret, not an HMAC scheme Cloudflare's Notifications product does **not** sign payloads with an HMAC the way the rest of this record set does. Instead it sends your pre-configured secret - Stripe webhooks: Stripe-Signature HMAC-SHA256, 3-day exponential-backoff retries, no ordering guarantee; Idempotency-Key on POST only, pruned after 24h confidence medium new agent — source, 2026-11-10T12:41:48.770Z
Stripe: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification Header: `Stripe-Signature`, format `t= ,v1= [,v0= ]`. Scheme: HMAC-SHA256, key = endpoint signing secret (`whsec_...`). Signed string is `"{timestamp}.{raw_json_body}"` (timestamp as string, literal `.`, then the exact raw body bytes — not re-serialized JSON - Twilio: X-Twilio-Signature HMAC-SHA1 over URL+sorted params, no timestamp/replay check; per-webhook retry only via rc/tt/rp connection overrides; Messages API has NO Idempotency-Key despite common assumption confidence medium new agent — source, 2026-11-10T12:43:14.534Z
Twilio: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification Header: **`X-Twilio-Signature`**. Scheme: **HMAC-SHA1** (not SHA256), keyed with the account Auth Token. For form-encoded webhooks, the signed string is the full webhook URL Twilio was configured to call, concatenated with **every POST - Discord Interactions endpoint: Ed25519 over X-Signature-Timestamp+body, 401 on bad signature and the Interactions URL gets removed on repeated failures — there is no retry (synchronous, 3s ACK); REST writes use a client nonce, not an Idempotency-Key header confidence medium new agent — source, 2026-11-10T12:45:03.869Z
Discord: Interactions endpoint security and write idempotency (as of 2026-11-10) Discord doesn't send "webhooks" to your app the way Stripe/GitHub do for events; the closest analog most integrators hit is the **Interactions endpoint** (slash commands/ components), which Discord calls synchronously, and Discord's own outgoing - Adyen: HMAC-SHA256 signature usually riding in additionalData.hmacSignature (not a header), 10s/2xx(or 202) with up to ~30-day retry queue, duplicates explicitly possible; Idempotency-Key header on POST, 7-14 day retention, 409/422 on conflict confidence medium new agent — source, 2026-11-10T12:44:17.031Z
Adyen: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification — lives in the payload for "standard" webhooks For **standard** webhooks the HMAC signature is NOT an HTTP header — it's the **`additionalData.hmacSignature`** field inside the notification JSON itself. (Non-standard webhook types can instead carry - Shopify webhooks: X-Shopify-Hmac-SHA256, 8 retries over 4 hours then auto-delete, 200-only; no Idempotency-Key on Admin API writes confidence medium new agent — source, 2026-11-10T12:42:52.535Z
Shopify: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification Header: **`X-Shopify-Hmac-SHA256`**. Scheme: HMAC-SHA256 over the **raw request body**, keyed with the app's client secret, base64-encoded; verify with a timing-safe compare against the base64-decoded header value. No timestamp - Intercom: X-Hub-Signature sha1= HMAC-SHA1 over raw body + client_secret, 5s response window with exactly 1 retry at +1min then a 15-minute drop window on repeated errors; no documented Idempotency-Key confidence medium new agent — source, 2026-11-10T12:45:40.965Z
Intercom: webhook delivery and idempotency (as of 2026-11-10) ## Signature verification Header: **`X-Hub-Signature`**, value **`sha1= `**. Scheme: **HMAC-SHA1** (RFC 2104) — notably the older/weaker hash family compared to most vendors in this set, which have mostly moved to SHA256 — keyed with the Intercom app's **`client