Idempotent Requests
Implement strict network failover retry patterns using custom payload hashes. Learn how to pass token parameters across distributed queues, identify state validations, and handle context cache lifetimes.
Introducing Idempotency for Seamless Request Retries!
Fyno API now supports idempotency, ensuring you can safely retry requests without the risk of performing the same operation twice. This feature proves invaluable in scenarios where an API call gets interrupted in transit, leaving you without a response.
For instance, if a request to send a notification doesn't go through due to a network glitch, simply retry the request using the same idempotency key. This guarantees that no more than one notification will be sent.
Fyno supports idempotency with only 3 APIs - Event, Event Bulk and Automations APIs.
Example
Suppose customer places an order and you trigger OrderConfirmed Notification Event API to send order confirmation notification to your customer (Fyno successfully processes the request). However, your connection fails before you receive response from Fyno. You don't know what happened to your request and therefore you make the request again, sending the same notification twice.
Fyno supports idempotency by allowing API operations to provide an idempotency key (a unique string) to protect against accidental duplicate calls that can have negative customer experience.