Contents

Purpose

This endpoint is used to identify a guest who scans an identifier generated by the RBI app (which could be an OTP or the Loyalty ID) at a client device (typically a POS or Kiosk terminal). OTP is always allowed, but Loyalty ID’s may or may not be allowed depending on configuration. Each user can only have one transaction ID open at a time. The latest transaction ID will always be kept and any other open transaction will be cancelled.

This endpoint should only be called during the first scan. Subsequent scans should call Identify (PUT) instead.

Request Format

Endpoint

POST /loyalty/v2/identify

Headers

Bearer token in JWT format as specified in https://rbictg.atlassian.net/wiki/spaces/IN/pages/3739288100.

Body

• identifier <string>: OTP (6 digit code) or Loyalty ID in UUID format.

• location: object identifying the location the guest is identifying from.

  • hasLoyalty <boolean> (optional): defaults to true. If false, then no points will be earned or burned for transaction and no rewards can be ordered.

  • storeId <string>: uniquely identifies the store where the guest is identifying from.

  • storeTransactionId <string>: uniquely identifies the store’s current transaction.

  • terminalId <string> (optional): identifies the POS or Kiosk terminal used in the restaurant

• content <boolean> (optional): whether the endpoint should return the list of offers and rewards that are visible to this guest. Defaults to false.

Example request

Response Format

Success response body

• transactionId <UUID>: unique identifier of the loyalty transaction created.

• balance <number>: this represents the number of loyalty points the user has. If this QR code was pre-selected with rewards, then this number already has those loyalty points temporarily deducted from total user’s loyalty points balance.

• loyaltyUser: object that indicates information about this loyalty user

  • created <string>: string that represents that date and time user loyalty account was created

  • id <string>: Loyalty ID of the user in UUID format

  • name <string>: name of the user that was saved upon account creation

  • tier <number> (optional): loyalty tier this user is in. Only applies for markets that have loyalty tier feature enabled. It can be “1” for guests that are in tier 1 or “2” for guests that are in tier 2.

• cart: an array that includes objects with the below fields for each product that is in the order basket.

  • externalreferenceId <string>: PLU of the product that was pre-selected in the app. This can be an offer or a reward.

  • quantity <number>: the amount of the above product that is in the loyalty order.

  • type <string>: the type of product. It could be Reward , Offer, Item or Combo

  • menuSelections(optional): an array that includes combos or sub-items within the product.

    • externalreferenceId <string>: PLU of the menu selection within the the product that was pre-selected in the app. This can be a combo or item PLU.

    • quantity <number>: the amount of the above product that is in the loyalty order.

    • type <string>: the type of product. It could be Item or Combo

    • menuSelections(optional): an array that includes sub-items within a specific product.

• content: array that includes all visible PLUs for the user related to offers and rewards in the market.

  • plu <string>: PLU of all rewards or offers that are visible to this guest.

Success response example

• Success response without content information

• Success response with content information

Error responses

• HTTP 400 (Bad Request) if the request body has an incorrect format. In this case, the response will include details about which specific field or fields have an incorrect format.

• HTTP 401 (Unauthorized) if the bearer token is missing or not valid.

• HTTP 404 (Not Found): in the following scenarios indicated in the code field of the error response:

  • "IdentifierNotFound": if the specified identifier was not found.

  • "StoreNotFound": if the specified storeId was not found.