Requesting products via REST API using store code in URL returns products from all stores

[Vossie1975]

Preconditions

• Magento 2.4-develop;
• Integration created;

Steps to reproduce

1. Create a website with code wb2.

2. Create a store st2 and assign it to the wb2 website.

3. Create a store view with code sv2 and assign to the new store.
   

4. Create product and assign only to wb2 website.
   

5. Perform REST API GET request using the store code in the URL, eg:
   GET /rest/default/V1/products/?searchCriteria[currentPage]=10

Expected result

Only products assigned to the test website are returned (or no products if none assigned).

Actual result

All products in the Magento instance are returned.

[ghost]

@Vossie1975, thank you for your report.
We've acknowledged the issue and added to our backlog.

[Vossie1975]

any idea when this bug wil be fixed (again)?

[paul-blundell]

Typical Magento. Another major bug that is being left to gather dust...

[Tiberriver256]

Any update?

[Vossie1975]

probably not....
Does not seem interesting for Magento to solve this.
This bug was previously in the system and would have been resolved then.
But is there again / still in it.
I have now reported this almost a year ago, but not a single update since that time.
Recently also other bugs found (in MSI function) but why would you still take the trouble to report it if nothing is done with it ....

[razza12]

Will this be resolved? Am still seeing this issue on 2.3.1

[Cyclonecode]

I am running magento 2.2.6 and this is a huge problem for us right now. Is there anyway to workaround this?

[Vossie1975]

dont think this will ever be fixed.
this is second time that this problem is in Magento and i have posted this more then a year ago and no response anymore in that time.
Only sollution (what we are also working on nowe) is to stop using magento.
We are building a new webshop now on other ecommerce software becouse of this problem.

[m2-assistant]

Hi @engcom-Charlie. 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.

[mshifo]

are there any updates ?

[Vossie1975]

wowww after only 3 1/2 years already a response.....
but never mind, fortunately within 1 and 2 months finally got rid of magento and to completely different software!

[ihor-sviziev]

@Vossie1975,
Sorry, I completely understand that your issue wasn't noticed for a huge amount of time.
I prefer re-opening this issue as it's still not fixed yet.

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-1231

[tuyennn]

Is anyone working on this?

[invertedfjord]

I can confirm that the issue still reproducing on 2.4-develop branch.

1. created website, store and store view:
   
2. created new root category and sub-category for 2nd store
   
3. created simple product, assigned to 2nd website:
   
   

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/products?searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8'

Expected result: Only one test product should be returned.

Actual result: ❌ Returned all products available in Magento

Other notes:

1. The same request with the filter applied using search criteria works fine (THIS IS WORKING WORKAROUND):

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/products?searchCriteria[filter_groups][0][filters][0][field]=store_id&searchCriteria[filter_groups][0][filters][0][condition_type]=eq&searchCriteria[filter_groups][0][filters][0][value]=sv2&searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8' 

✔Only one test product is returned

2. Fetching categories works fine w/o applying filter using search criteria:

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/categories?searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8' \
--header 'Cookie: PHPSESSID=dbov1elserndboromibgi6sl0l'

✔ The only categories returned for 2nd store

2. Fetching categories works fine with applying filter using search criteria:

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/categories?searchCriteria[filter_groups][0][filters][0][field]=store_id&searchCriteria[filter_groups][0][filters][0][condition_type]=eq&searchCriteria[filter_groups][0][filters][0][value]=sv2&searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8'

✔ The only categories returned for 2nd store

I can confirm that the issue still reproducing on 2.4-develop branch.

1. created website, store and store view:
   
2. created new root category and sub-category for 2nd store
   
3. created simple product, assigned to 2nd website:
   
   

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/products?searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8'

Expected result: Only one test product should be returned.

Actual result: ❌ Returned all products available in Magento

Other notes:

1. The same request with the filter applied using search criteria works fine (THIS IS WORKING WORKAROUND):

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/products?searchCriteria[filter_groups][0][filters][0][field]=store_id&searchCriteria[filter_groups][0][filters][0][condition_type]=eq&searchCriteria[filter_groups][0][filters][0][value]=sv2&searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8' 

✔Only one test product is returned

2. Fetching categories works fine w/o applying filter using search criteria:

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/categories?searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8' \
--header 'Cookie: PHPSESSID=dbov1elserndboromibgi6sl0l'

✔ The only categories returned for 2nd store

2. Fetching categories works fine with applying filter using search criteria:

curl --location -g --request GET 'https://a157f32be171e2a736d57b2a1dece736-2-4-develop.instances.magento-community.engineering/index.php/rest/sv2/V1/categories?searchCriteria[filter_groups][0][filters][0][field]=store_id&searchCriteria[filter_groups][0][filters][0][condition_type]=eq&searchCriteria[filter_groups][0][filters][0][value]=sv2&searchCriteria[pageSize]=50&searchCriteria[currentPage]=1' \
--header 'Authorization: Bearer eyJraWQiOiIxIiwiYWxnIjoiSFMyNTYifQ.eyJ1aWQiOjEsInV0eXBpZCI6MiwiaWF0IjoxNjMxNzA2ODQyLCJleHAiOjE2MzE3MTA0NDJ9.y38aigVekrNE5KkogtWAUf3jtLRzj0H_aRfViJcWKp8'

✔ The only categories returned for 2nd store

@ihor-sviziev Does this workaround that you mentioned query the DB in the same way?

[hugocore]

For those reading and following this issue, there's a workaround:

https://<DOMAIN>/rest/<STORE_CODE>/V1/products?
searchCriteria=&
searchCriteria[filterGroups][0][filters][0][field]=store_id&
searchCriteria[filterGroups][0][filters][0][value]=<STORE_CODE> 

Essentially you can scope products by a store if you pass the store code as a custom search criteria.

[invertedfjord]

For those reading and following this issue, there's a workaround:

https://<DOMAIN>/rest/<STORE_CODE>/V1/products?
searchCriteria=&
searchCriteria[filterGroups][0][filters][0][field]=store_id&
searchCriteria[filterGroups][0][filters][0][value]=<STORE_CODE> 

Essentially you can scope products by a store if you pass the store code as a custom search criteria.

We did extensive testing and passing the store code as a search param does not work reliably. If you pass the store ID for products it does work most of the time.

Testing on many Magento 2 accounts on various versions came to the following results.

1. Store code in the URL is essentially useless.
2. Store ID passed as a search param does work for 80% of accounts. Some accounts return 500 or 400 errors and sometimes it's still not store scoped. (Not sure why maybe from some customizations on the store front)

[howdyravi]

Any update on this ?

[nidhigupta13-ey]

@magento I am working on this