Versions Compared

Old Version 20

changes.mady.by.user Lopes da Costa, Valentina

Saved on

compared with

New Version 21

changes.mady.by.user Lopes da Costa, Valentina

Saved on

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:

    • "TransactionNotClaimable" : the transaction status is not Pending or Claimed, or the transaction status in the endpoint call payload is not Pending or Claimed.

    • "TransactionInsufficientPoints": the user want to redeem more points than the user has.

    • "RedeemRewardError": when the Reward is redeemed in a store with loyalty disabled.

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

    • "TransactionNotFoundError": the transaction (specifically the transaction id) was not found.

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