Skip to main content

Idempotency

Webhook Idempotency​

Webhooks use at-least-once delivery. Your handler should be idempotent — processing the same event twice should produce the same result.

Deduplication Strategy​

  • Use the booking_id + event combination as an idempotency key
  • Track processed events in your database
  • Booking metadata flags (e.g., credentials_requested) prevent duplicate processing

Booking Idempotency​

  • Booking creation checks for time slot conflicts before committing
  • Duplicate booking attempts for the same time slot return a 409 Conflict

Next Steps​