A dry request is a test request that is checked by Talon.One but that is not executed.
To mark an Integration API request as dry, add the optional query parameter
No data about this request and its response is stored in Talon.One's database.
We added this feature to realize What if scenarios. For example:
- What if the end-user adds this product to their cart?
- What if the end-user applies this coupon to their order?
- Your customer isn't doing a real-life step in an order process
Additionally, you can check the output of a rule without affecting reportings or updating any dataset.
Example scenario 1
- Your end-user is looking at a product page
- You are firing a customer session update, pretending that the end-user already put this item in their cart
- If the API response includes a per item discount for this cart item, the discounted price gets rendered on the page
If you plan on using dry runs for such a use case, implement an intelligent caching solution on your side. Avoid hitting the Talon.One API on every single page visit.
Example scenario 2
- Your end-user puts an item in their basket and proceeds to checkout.
- Your end-user has reserved coupons.
- You are firing a session update to test if this reserved coupon resulted in a discount on this order.
- If it does, the coupon gets applied automatically and the end-user gets a notification.