Rest API get stock_items with low stock not behaving like other get methods

[NotAndD]

Preconditions

1. Install Magento 2.1.3 with sample data.
2. Set up Rest integration.

Steps to reproduce

1. Retrieve stock_item list of low stock items sending a Rest request to /V1/stockItems/lowStock/ with method GET, query parameters scope_id and qty as specified in the documentation. Rest request like this: rest/default/V1/stockItems/lowStock/?scopeId=0&qty=10.

Expected result

1. As for all other Rest methods available that returns a list taking filter parameters and as the documentation specify, if no page_size is given, all results of the query should be returned.

Actual result

1. Only one stock item is returned, in addition, search_criteria has a different structure from other methods, with a limit field that is automatically set like this:

"limit": [
      "1",
      "0"
    ]

Notes

Either changing the documentation (fast solution) or even better, uniforming this method with all the other available methods, making it accept a filter and not only page filter parameters (page_size and current_page).

Additional info

• Reproducible on Magento 2.4-develop
• The way it can be reproduced via Swagger

1. In your web browser open http://{magento2 instanse}/swagger#/integrationAdminTokenServiceV1/integrationAdminTokenServiceV1CreateAdminAccessTokenPost click Try it out
   
2. Set admin User name and Passwod and click Execute
3. Copy the token from the Response body
   
   and Paste it into api_key field in the top right corner. Click Apply
   
4. Open catalogInventoryStockRegistryV1 - GET /V1/stockItemslowStock clcik Try in out
   
5. Set scopeId to 0 qty to 10. Click Execute
   

Actual Result:

[magento-engcom-team]

@ziliquas, thank you for your report.
We've created internal ticket(s) MAGETWO-81168 to track progress on the issue.

[timpea]

Is there any update on this bug?

[atsareva]

Any updates here?

[Hexmage]

A workaround is setting the page_size parameter to a very large number.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

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

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-30059 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[gabrieldagama]

These API is deprecated, please have a look at the documentation below to get more details on the new APIs that should be used instead:
https://devdocs.magento.com/guides/v2.4/inventory/index.html
https://devdocs.magento.com/guides/v2.4/inventory/catalog-inventory-replacements.html

Thanks.