What are "Dry Requests"?
By adding an optional query parameter dry=true to any Integration API call leads to the following:
No data about this request and its response will be stored in our database.
We added this feature to realize "What if" scenarios e.g.:
- "What if" the end-user would add this product to their cart?
- "What if" the end-user would apply this coupon to their order?
- Your customer is NOT doing an actual, 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
Note: If you plan on using dry runs for such a use case, please implement an intelligent caching solution on your side. Please 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 would result in a discount on this order.
- If it does, the coupon gets auto-applied and the end-user gets a notification