ChatPulse

Retry Policy

How ChatPulse handles delivery retries for Webhooks and API calls.

API Requests

If our API returns a 429 Too Many Requests or a 5xx Server Error, we recommend implementing an exponential backoff retry mechanism in your client code. Our official SDKs implement this automatically.

Webhook Deliveries

If your webhook endpoint does not respond with a 2xx status code within 5 seconds, ChatPulse will attempt to redeliver the event using an exponential backoff schedule:

  • Immediately
  • 1 minute
  • 5 minutes
  • 30 minutes
  • 2 hours
  • 12 hours

If the delivery fails after all retries, the webhook event is marked as failed and can be manually replayed via the Dashboard.