> ## Documentation Index
> Fetch the complete documentation index at: https://developers.loyaltylion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

<Update label="4 September 2026">
  ## Order-count tiers

  A program can now set its tier thresholds as a number of qualifying orders,
  alongside the existing points and spend modes. Nothing changes for points or
  spend programs. The additions below only appear when a program uses order-count
  tiers:

  * `tier_configuration.boundary_mode` in the [Get
    Configuration](/headless-api/2025-06/configuration/get-configuration) response
    can be `orders`. Each non-conditional tier then has `kind: "orders"`, an
    integer `lower_bound`, and an integer or `null` `upper_bound`, both
    inclusive counts of qualifying orders

  * `tier_membership.progress` on the customer, returned by [Initialize
    Session](/headless-api/2025-06/customers/initialize-session) and [Get
    Customer](/headless-api/2025-06/customers/get-customer), has a `kind: "orders"`
    variant with `tier_orders`, `orders_needed_for_upgrade` and
    `orders_needed_for_renewal`, mirroring the points and spend variants

  A qualifying order is paid or partially paid, not cancelled, and not fully
  refunded. A partially refunded order still counts as one order. If the program
  sets a minimum qualifying order value, an order only counts when its value, net
  of refunds and gift cards, meets that minimum. See
  [Tiers](/headless-api/2025-06/configuration/get-configuration#tiers).
</Update>

<Update label="28 August 2026">
  ## Customer session tokens

  Most Headless API endpoints accept a [customer session
  token](/headless-api/session-tokens) in place of an API key, so they can be
  called directly from a shopper's browser or mobile app.

  A session token is a signed credential you generate yourself, scoped to one
  customer on one site and to the `read` / `write` scopes you grant it. There is
  no API call to get one: you sign it with a key we publish to your store,
  which means a Shopify theme can render one in Liquid with no backend at all.

  This means you can now make calls to the Headless API directly from the
  client, instead of proxying them through your backend first.
</Update>

<Update label="25 August 2026">
  ## Referrals

  The Headless API now supports the full referral loop, so shoppers on a
  headless storefront or mobile app can share referral links, and their
  friends can claim the referral incentive and complete the referral:

  * The [Claim Referee Incentive](/headless-api/2025-06/referrals/claim-referee-incentive)
    endpoint exchanges the `ll_ref_id` from an inbound referral link for a
    discount voucher code to show the referred shopper

  * The [Track Share](/headless-api/2025-06/referrals/track-share) endpoint
    records shares so they appear in your referral analytics

  See the new [Referrals guide](/headless-api/guides/referrals) for the
  end-to-end flow, including order attribution and mobile deep links.
</Update>

<Update label="8 June 2026">
  ## Enroll customers into the program

  The [Enroll Customer](/headless-api/2025-06/customers/enroll-customer) endpoint
  can be used to explicitly enroll a customer into your program, so a shopper can
  join from your own storefront or mobile app, for example from a "Join the
  program" button.

  This is particularly useful if your program is configured for opt-in enrollment,
  where initializing a session deliberately doesn't enroll anyone.
</Update>

<Update label="29 July 2025">
  ## Set customer birthdays and subscribe to email marketing

  * The [Set Birthday](/headless-api/2025-06/customers/set-birthday) endpoint
    can be used to set a customer's birthday, so you can capture it as part of
    your storefront or mobile app and send it to LoyaltyLion where it can be used
    to gift a customer points or a reward for their birthday

  * The [Subscribe to Email Marketing](/headless-api/2025-06/customers/subscribe-email-marketing)
    endpoint can be used to subscribe a customer to email marketing. This is limited
    to Shopify stores for now, and will update the customer's email marketing consent
    with Shopify. If applicable rules are configured, they will be automatically
    triggered, such as awarding a customer with points or a reward for subscribing

  ## Complete rules for customers

  Complete interactive rules for customers using a set of new endpoints:
  [Clickthrough](/headless-api/2025-06/complete-rules/clickthrough),
  [Facebook Like](/headless-api/2025-06/complete-rules/facebook-like),
  [Instagram Follow](/headless-api/2025-06/complete-rules/instagram-follow),
  [TikTok Follow](/headless-api/2025-06/complete-rules/tiktok-follow),
  [Twitter/X Follow](/headless-api/2025-06/complete-rules/twitter-follow),
  [Custom](/headless-api/2025-06/complete-rules/custom)

  These endpoints should be called once the customer has completed the relevant
  action, such as visiting a URL, liking a Facebook page or following a TikTok user,
  and will immediately complete the rule for the customer and award them points
  or a reward, assuming they're eligible.
</Update>

<Update label="17 July 2025">
  ## Customer history

  Endpoints that return a Customer object, such as the
  [Get Customer](/headless-api/2025-06/customers/get-customer) API and reward
  redemption endpoints, now return the customer's recent point, tier and reward history
  under the `customer.history` property.
</Update>

<Update label="8 July 2025">
  ## Free product rewards

  The Headless API now supports the redemption of free product rewards when
  used with a Shopify storefront.

  See the [Free Product redemption](/headless-api/2025-06/reward-redemption/free-product)
  endpoint, and our [implementation guide](/headless-api/guides/hydrogen/free-product-rewards) for Shopify Hydrogen.

  If you're using a different frontend framework, you can still redeem free
  products (it's not Hydrogen specific). Review the Hydrogen guide for an overview
  and adapt to your framework, or get in touch with us if you need help.
</Update>