...

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.

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

Request Format

Endpoint

POST /loyalty/v2/identify

...

Example request

POST /loyalty/v2/identify
{
    "identifier": "123456",
    "location": {
        "storeId": "9999",
        "terminalId": "0", 
        "hasLoyalty": true 
    },
    "content": true
}

...

• 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 403 404 (Forbidden)Not Found): in the following scenarios indicated in the code field of the error response:

  • "IdentifierNotFound": if the specified identifier

  is

  • was not

  valid

  • found.

  HTTP 404 (Not Found)

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