Sender Rate Limits

Preconfigured sender rate-limit rules and 429 backoff policies for Stripe, Shopify, GitHub, and custom providers.

Third-Party Provider Rate Limits

Major webhook senders impose strict delivery constraints and concurrency rules:

ProviderConcurrency & ConstraintsFailure Handling
Stripe100 concurrent requests; max 5s timeout.Retries over 3 days (exponential backoff). Suspends endpoint on high failure rate.
ShopifyExpects response in < 5s. Max 19 retries over 48h.Automatically unsubscribes and deletes the webhook endpoint after repeated failures.
GitHubExpects response in < 10s.Stops delivering if deliveries time out consistently.

Note:

The Shopify Danger: If your server goes down for maintenance and fails Shopify webhooks for 48 hours, Shopify will permanently delete your webhook subscription. By pointing Shopify to Bunnylynk, Bunnylynk returns 200 OK in 15ms, preventing endpoint cancellation while your server updates!

Handling Downstream 429 Too Many Requests

When your downstream server returns an HTTP 429 Too Many Requests:

  1. Retry-After Header Parsing: If your destination responds with a Retry-After: 30 header, Bunnylynk honors the downstream server's request and sleeps for exactly 30 seconds before retrying.
  2. Adaptive Concurrency Throttle: Bunnylynk automatically drops the active concurrency limit by 50% for 2 minutes to allow your downstream service to recover.
  3. Queue Smoothing: Backlogged requests are smoothed into a steady flow matching your configured rate_limit_per_second.

Next: Learn about the Rules Engine & Transformations.