Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

All error responses use the standard https://rbictg.atlassian.net/wiki/spaces/RDP/pages/4231725617/LLoyalty+API+v1+-+Error+Responses format.

  • 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:

    • "IdentificationFailed": the sent identifier was not correct (e.g. not an OTP code) but complies to a loyalty ID number format, then it’s detected as a LOYALTY_ID by accident.

  • HTTP 401 (Unauthorized) if authentication headers are missing or not valid.

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

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

    • "UserNotFoundError": the Loyalty user (specifically the loyalty id) was not found.

    • "RewardNotFoundError": the reward being pre-selected was not found.

    • "OfferNotFoundError" : the offer being pre-selected was not found.

  • HTTP 422 (Unprocessable Entity) if identifier cannot be processed

    • "OrderSelectionStatusUnclaimable": the identifier (e.g. OTP) was already used.

    • "InvalidIdentifier": the identifier was not a valid type.

    • "IdentifierTypeDisabled": the detected identifier type is not supported in the market.