Offer redeemers and request middleware

Offer redeemers are live for all offers

Every offer now uses redemption methods. Attach a redemption method when creating an offer in the console, then redeem it through the offer redemption API endpoint, which runs the attached redemption workflow at the edge. Redemption workflows come with built-in Stripe helpers and receive the offer token in their input, redemption events appear in observability with full detail, and redemptions fire system triggers like surface decisions and access checks. To get started, see How to redeem a Stripe Checkout offer.

Request middleware is generally available

Middleware stacks now run in front of all API traffic, both custom Endpoints and the native endpoints for surface decisions, access checks, counters, and offer redemptions. Middleware can set context properties for downstream workflows, tag traffic with built-in or custom bot tags, and return multiple actions executed in order. Middleware workflows and stacks are managed from their own console screens, and handlers are fully typed in the editor. See Middleware Workflows.

Cookies and Fastly geolocation in workflow context

Request cookies are now forwarded to surface decision calls and exposed in the workflow context, so a workflow can read cookie values when deciding what to serve. See How to surface cookies at the edge. Fastly-fronted setups also now receive geolocation data in the workflow context, matching the other proxies.

Improvements and fixes

• APIThe identity object is now optional in the Webscale API schema.
• ConsoleFile changes made by the assistant now reliably reach the experience editor.
• ConsoleProduct search returns more Stripe prices per product, so long price lists no longer appear incomplete.
• ConsoleThe features list no longer drops items or blocks next-page navigation.
• ConsolePay-as-you-go billing checkout now collects a business name and address.