New endpoint for issuing bonus points through the API
(RTL-6682, RTL-6683, RTL-6684)
Three new methods for handling the issue of bonus points are now available:
Detailed information can be found in our Swagger documentation here
Improvements
Header | Description |
| Typo in API calls should not result in 500 (RTL-6878) | Typos (syntax errors) in requests for all calls to BonusService Api return 400 bad request with appropriate validation messages. |
Import bonus checks balance
(RTL-4176)
A new import contract has been added, which allows for importing a new bonus check balance for a given member identity.
The job that imports the new balance redeems or issues new bonus checks based on the members previous bonus checks balance.
The contract can be found here: Swagger
Improvements
Header | Description |
Improved error handling in Bonus check API (RTL-6621) | Improved handling of errors that occur when user is not using the Authorize/Commit/cancel of bonus checks in the correct way. Instead of getting 500 internal server error the correct 400 error message is returned. |
Update last used date on bonus checks (RTL-6609) | In some scenarios the "last used date" was not updated when a bonus check was used, this has been corrected and the bonus check UI now show the proper "last used dates". |
...
We have also added a new system parameter which decides if Bonus Service should validate member data
against our internal member master or not:
Improvements
Header | Description |
Bonus checks UI do not show any bonus checks (RTL-6318) | Fixed an issue where bonus checks did not appear in the Bonus checks UI. |
...
The three first letters of the bonus check code will contain the prefix of the given bonus check type.
Example of a bonus check with the type "Return": RET8W76THV659
Improvements
Header | Description |
|---|---|
| Bonus check details UI improvements (RTL-5855) |
|