The subscription/created webhook now includes a new prepaidIntervalCount boolean in the billingPolicy object, improving visibility into prepaid subscription billing cycles at the time of creation.

What's New?

A new prepaidIntervalCount boolean is now available in the billingPolicy object of the subscription created webhook. When used together with the prepaid billing interval count and delivery interval count, it allows brands to accurately calculate the number of orders in a prepaid cycle. This enhancement is especially useful for brands relying on third-party fulfillment services, as it enables better inventory forecasting and operational planning based on newly created subscriptions.

New loyalty storefront API endpoints are now available to fetch and redeem loyalty points for customers.

What's New?

We’ve introduced two new loyalty endpoints that let you power loyalty experiences directly in your headless subscriber portal:

1. Fetch customer loyalty information: Allows you to fetch customer loyalty points information.
2. Redeem customer loyalty points: Allows you to redeem customer's loyalty points against one of their subscriptions.

Things to remember:

1. A loyalty integration must be connected before using these APIs. To connect the integration, Navigate to Loop > Tools & apps > Apps.
2. Currently supported integration: Rise.ai only.

• Read all subscriptions (Admin API): new optional createdAt time-range filters have been added to support incremental syncs using Unix epoch:
  • createdAtStartEpoch
  • createdAtEndEpoch

• Read all past orders (Admin api) : new optional shopifyCreatedAt time-range filters have been added (based on Shopify order creation time):
  • shopifyCreatedAtStartEpoch
  • shopifyCreatedAtEndEpoch

Compatibility / Impact

No breaking changes: These are additive query parameters; existing requests behave the same if filters aren’t provided.

What's new?

Subscription lines information is now available in the Subscription object returned by the read subscription for customer admin API endpoint.

This enables you to fetch line details (e.g., subscription line items) directly from the subscription payload without requiring a separate follow-up call.

New Endpoints:

• Read all past orders: You can now retrieve all past orders associated with a specific customer. This endpoint allows access to the customer’s complete order history across all subscriptions. Link here.
• Read all scheduled orders: This endpoint allows you to retrieve list of all scheduled order for a customer across all subscriptions. Link here.

These additions provide greater flexibility and more detailed access to customer order data through the Storefront API.

What's New?

The List Subscriptions endpoints in the storefront API now support a status filter that lets you query subscriptions by their current subscription state. This enhancement reduces payload sizes, minimizes client-side filtering, and improves performance for headless storefronts and customer portal.

Subscription status filters that can be used:ACTIVE, PAUSED, CANCELLED, EXPIRED

Refer to List Subscriptions endpoint for more details.

You can now retrieve delivery method details for each subscription directly from the List subscriptions storefront API endpoint. This enables showing accurate delivery information in custom or headless subscriber portals.

What’s New?

The deliveryMethod object is now returned for each subscription in the List subscriptions storefront API response. You can use this to display the delivery method name or code wherever you surface subscription details.

Example response snippet:

"deliveryMethod": { "code": "Express", "title": "Express" }

• code - Internal or system identifier for the delivery method.
• title - Display label for the delivery method, intended for customer-facing UI.

New mystery reward storefront API endpoints are now available to fetch, claim, and track mystery rewards for subscriptions in any locale.

What's New?

We’ve introduced three new mystery reward endpoints that let you power reward experiences directly in your headless subscriber portal:

1. Mystery reward endpoint: Fetches mystery reward details for a given subscription ID in a specific locale. Use this to show eligible mystery rewards, messaging, and visuals on the customer portal.
2. Claim mystery reward: Allows you to claim a mystery reward on a subscription by passing the rewardId (mystery reward ID). rewardId can be fetched in Mystery reward endpoint.
   Claim mystery reward endpoint is typically triggered when the subscriber clicks to redeem their mystery reward.
3. Add viewed logs for mystery reward: Logs when a mystery reward is viewed for a subscription. These view events can later be used to analyze impressions and conversion rates.
   **Please note: **This endpoint should only be triggered if a customer views the mystery reward but doesn't claim the reward.

These endpoints return the following fields:

• configTexts: Customer-facing texts used to render the mystery reward experience.
• mysteryRewardType: The type of reward, e.g., gift or discount.
• subscriptionOrderNumber: The relevant order number on the subscription associated with the reward.
• source: The feature source triggering the reward, such as flows or streaks.
• rewardId: The unique ID of the mystery reward, used to claim the reward via the claim endpoint.

You can now reschedule the next order date for subscriptions paused with a definite period using the Reschedule subscription endpoint. This helps you adjust billing dates without unpausing or recreating the subscription.

What's New?

Paused subscriptions with a definite next order date can now be rescheduled via the reschedule subscription endpoint by passing the new date in epoch format. The rescheduled order will use the global billing hour (if configured) or fall back to the original billing time of the order being rescheduled.

The ability to reschedule order in paused state will help in adjusting the billing dates without unpausing or recreating the subscription.

Things to Keep in Mind

1. The paused subscription will auto-renew one day before the upcoming order notification date set in notification preferences.
2. Subscriptions paused indefinitely cannot be rescheduled via this endpoint, as no future order queue is created in such cases.

Prepaid subscription marked for cancellations can now be easily detected with the new isMarkedForCancellation field which is added in the Read subscription details endpoint.

A dedicated subscription/markedForCancellation webhook is added to allows automation of cancellation-related workflows.

What's New?

1. New boolean in Read subscription details endpoint: A new boolean field, isMarkedForCancellation, is now available on the Read Subscription Details API response.
   • true - the prepaid subscription is scheduled to cancel at the end of its current prepaid cycle.
   • false - the subscription is not marked to cancel at cycle end.
2. New webhook topic: subscription/markedForCancellation A dedicated webhook event is now emitted when a prepaid subscription is marked to cancel at the end of its current cycle.
   • Fires at the moment the subscription is flagged for cancellation.
   • Can be used to trigger downstream workflows (notifications, CRM updates, reporting, etc.) to save the churn.

Benefits

• Clearer lifecycle visibility: Easily distinguish between active prepaid subscriptions and those scheduled to end after the current cycle.
• Better automation: Use the subscription/markedForCancellation webhook to automate retention flows, downstream cancellations, or internal alerts without polling.

Things to Keep in Mind

1. isMarkedForCancellation is only relevant for prepaid subscriptions; standard (non-prepaid) subscriptions will have is prepaid key false.
2. You can subscribe to the new subscription/markedForCancellation webhook from [here].