Skip to main content
Spark360 retries failed deliveries, so subscribers should process webhook events idempotently.
  • Use event_id as your idempotency key
  • Store processed event_id values in your system
  • Ignore duplicate event_id values on retry

​
Why this matters

  • Retries are expected for transient failures
  • Duplicate HTTP deliveries can occur by design during retry windows
  • Idempotency prevents duplicate CRM writes and repeated automations