This is the legacy version of Loyalty API integration that vendors are using. This does not supports multi-scanning and updating an order after it was started.
Brands and markets want to offer up an in-store loyalty experience where users can earn points and redeem points for in-store orders. This will require an integration between the POS and the RBI Loyalty Platform.
Desired In-store Loyalty User Flow
User identifies themselves as a loyalty user at the POS using identification mechanism (i.e. 6-digit short, code, QR code, etc.)
The identification may include pre-selecting rewards and/or offers within the app similar to the in-store loyalty experience
Upon successful identification:
Any pre-selected rewards and/or offers are injected into the POS order
User’s information is populated within the POS terminal (i.e. name, points balance)
User is able to proceed with placing their order by selecting desired items/combos
User completes order at POS and gets their food
General API Guidelines
Region {reg}
variables:
euc1
EU Timezone Marketsapse1
APAC Timezone Marketseuw3
Iberia Timezone Market
Environment {env}
variables:
dev
staging
qa
prod
Brand {brand}
variables:
bk
plk
fhs
All API requests should include the following in the header:
x-region
field. The value passed in this field should be the 2-character iso country code.x-api-key
field. The value passed in this field will be an environment, vendor and brand specific API key.x-user-datetime
field. The value passed in this field should be the local iso datetime string.
For international markets (all markets but US and CA), all endpoint URLs start with {reg}- e.g. https://euc1-staging-bk-loyalty-middleware.rbictg.com/loyalty/identify