How it works
Repeating a request with the same idempotency key should not create another deal or repeat a payment. Integration brings together customer records, telephony events and business workflows. Correct operation depends on consistent identifiers, synchronisation rules and permissions.
Business example
A duplicate webhook delivery does not create a second deal when the receiver recognises the event identifier.
What to consider
Test API failures, duplicate events, mandatory fields and recovery after temporary outages. Avoid exposing customer data unintentionally.