4th Nov 2020

Dry Requests

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.

Use cases

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

  1. Your end-user is looking at a product page
  2. You are firing a customer session update, pretending that the end-user already put this item in their cart
  3. 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

  1. Your end-user puts an item in their basket and proceeds to checkout
  2. Your end-user has reserved coupons
  3. You are firing a session update, to test if this reserved coupon would result in a discount on this order.
  4. If it does, the coupon gets auto-applied and the end-user gets a notification
Still need help? Get in touch!
Last updated on 4th Nov 2020

Was this article helpful?

Thank you! You have already voted

If you’d like a member of our support team to respond to you, please send a note to support@talon.one