Magento 2.2.7 - Unable to add tier price with 0 value via API

[andrewbgittus]

Preconditions (*)

1. Magento version 2.2.7

Steps to reproduce (*)

1. Send an API request with a tier price value of 0.

POST http://xxx.xxxx.com/magentov2/index.php/rest/V1/products/TEST/group-prices/1/tiers/20/price/0 HTTP/1.1
Authorization: Bearer xx0xxx0x0xx0xx00xxx00xx0x0xxxx0x
Accept: application/json, text/json, text/x-json, text/javascript
User-Agent: RestSharp/100.0.0.0
Host: dev.zynk.com
Content-Length: 0
Accept-Encoding: gzip, deflate
Connection: Close

Expected result (*)

1. Within the Magento UI it is possible to set a tier price value to 0 so I would have expected the API to allow the same and return a successful response.

Actual result (*)

HTTP/1.1 400 Bad Request
Date: Tue, 09 Apr 2019 08:30:45 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 39
Connection: close
Cache-Control: public, max-age=31536000
Expires: Wed, 08 Apr 2020 08:30:45 GMT
Vary: User-Agent
X-UA-Compatible: IE=edge
X-Turbo-Charged-By: LiteSpeed
Server: cloudflare
CF-RAY: 4c4b1eec6d3a6aa9-LHR

{"message":"Please provide valid data"}

[m2-assistant]

Hi @andrewbgittus. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@andrewbgittus do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[m2-assistant]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[ghost]

Hi @andrewbgittus . Thank you for your report.
The issue has been fixed in #18604 by @maheshWebkul721 in 2.2-develop branch
Related commit(s):

• 8084aa985c10208c1ee5bfd14ab31014bd4edfd4
• 8296637b258a9d03f81304bf00724cee553da029
• 42839360380bc3783e1840b0ff69eb922e97a99d
• 899a8a30d14907f07887a814060712a4b163efdb

The fix will be available with the upcoming 2.2.8 release.