Listing Offers and Rewards for Kiosk UI

Overview

To display valid offers and rewards on the UI, the client needs to retrieve data from two sources: the Loyalty Engine (Through the Loyalty Middleware) and Sanity (RBI’s CMS). The Loyalty Engine will provide incentives for which the user is "eligible," meaning they satisfy all necessary criteria (rules). Meanwhile, Sanity will offer information about active incentives, and reward categories, as well as all visual display content, such as names, images, descriptions, and more.

The client must hit both of the previously mentioned data sources and intersect the data to decide what to present. The sequence in which these queries are executed will depend on the client and its implementation. It is advised to first query Sanity for all "sorted offers" (active system-wide offers), “config offers” (possible personalized offers for any given user), and "reward categories" (active rewards), and then utilize those identifiers to request pertinent information from the Loyalty Engine.

Querying Sanity using GraphQL

GraphQL URL (Playground Available): https://czqk28jt.api.sanity.io/v1/graphql/dev_bk_us/default

• Replace dev_bk_us with the {{stage}}_{{brand}}_{{country}} that you desire to query.

• Sanity GraphQL can be hit via a POST request. Please reference the POST URL structure for each of the sample queries below.

• Please use this playground to play with the queries below and examine the schema for fields you may wish to request.

Example Offers Query

• The _id is subject to the dataset you are using. For the most part, it will be feature-loyalty-offers-ui-singleton, however, some markets have drifted from this convention

• Sample URL if using a REST client - https://czqk28jt.api.sanity.io/v1/graphql/dev_bk_gb/default?query=query getSanityOffers { LoyaltyOffersUI(id: "feature-loyalty-offers-ui-singleton") { sortedSystemwideOffers { _id name { enRaw } } liveConfigOffers { _id name { enRaw } } } }

query getSanityOffers {
	LoyaltyOffersUI(id: "feature-loyalty-offers-ui-singleton") {
    sortedSystemwideOffers {
      _id
      name {
        enRaw
      }
    }		
    liveConfigOffers {
      _id
      name {
        enRaw
      }
    }
  }
}

Example Rewards Query

• The id is subject to the dataset you are using. For the most part it will be reward-list-singleton, however some markets have drifted from this convention

• Sample URL if using a REST client - https://czqk28jt.api.sanity.io/v1/graphql/dev_bk_us/default?query=query getSanityRewards { RewardList(id:"reward-list-singleton") { rewardCategories { _id label { en } rewards { ... on Reward { _id name { en } } } } } }

query getSanityRewards {
  RewardList(id:"reward-list-singleton") {
    rewardCategories {
      _id
      label {
        en
      }
      rewards {
        ... on Reward {
          _id
          name {
            en
          }
        }
      }
    }
  }
}

Querying Loyalty Engine

URL - https://dev-bk-loyalty-middleware.rbictg.com/graphql

• Replace dev-bk with the {{stage}}-{{brand}} that you desire to query. For all markets other than US/CA, you will need to prefix the url with the AWS region that your market lives in. Please communicate with RBI reps to know which region your market is hosted. Example url for ES (Spain) would be https://euc1-dev-bk-loyalty-middleware.rbictg.com/graphql

• Please use this playground to play with the queries below and examine the schema for fields you may wish to request

• Some where filters that may be relevant to Kiosk

  • ids - a collection of engine ids for offers/rewards. This is the loyaltyEngineId field on every sanity offer/reward document

  • omitInvalids - This controls whether invalid incentives will be returned. Only incentives that failed “fixable” rules will be returned if this is set to false. A fixable rule is one that the user can change behavior to make the rule pass, like the minSpend, the user can add more items to their cart to meet the requirement. An absolute failure like date-band will not be returned regardless of what the value of this filter is

    • This is useful for displaying error / in-line messages in the UI

  • serviceMode - some incentives can only be redeemed if the service mode meets the required ruleset

  • storeId - some incentives can only be redeemed at certain stores

  • subtotalAmount = some incentives require a minimum spend

  • cartEntries - some incentives require certain items to be in the cart, this rule uses the sanity id of each rbi product

  • paymentMethod - some incentives require certain payment methods to be used

Example Offers Query

query getLoyaltyOffers {
  loyaltyOffersV2(loyaltyId: "some-user-id", where: { omitInvalids: false }) {
    id
    name
    errors {
      code
      ruleId
    }
  }
}

Example Offers Query Response

{
  "data": {
    "loyaltyOffersV2": [
      {
        "id": "a4c24211-2d36-47be-bad8-8deea437dbfa",
        "name": "$6 Let's Get This Bacon Meal",
        "errors": null
      },
      {
        "id": "fbba4e93-eecd-42b6-a4ed-333856d47bda",
        "name": "Delivery Offer - $8 The Spicy One Meal",
        "errors": null
      },
      {
        "id": "6646b80b-dea9-4bf4-81f5-390554926987",
        "name": "Loyalty Upsize Swap",
        "errors": [
          {
            "code": "unsatisfied-cart-requirements",
            "ruleId": "cart-requirement"
          }
        ]
      }
    ]
  }
}

Example Rewards Query

query getLoyaltyRewards {
  loyaltyRewards(loyaltyId: "some-user-id", where: { omitInvalids: false }) {
    id
    name
    errors {
      code
      ruleId
    }
  }
}

Example Rewards Response

{
  "data": {
    "loyaltyRewardsV2": [
      {
        "id": "3b5bdddc-c7c9-42d8-9332-b0c3f36c8e1c",
        "name": "Value Powerade Zero",
        "errors": null
      },
      {
        "id": "728aaedd-3234-4eae-89af-35cd5672adcb",
        "name": "Large Dr. Pepper",
        "errors": null
      },
      {
        "id": "480122d7-86ff-4db0-965c-7dbb72bb5179",
        "name": "Value Soft Drinks",
        "errors": null
      }
    ]
  }
}