Magento2: Catalog Price Rule not working for magento2 rest api

Created on 5 Jul 2018  路  11Comments  路  Source: magento/magento2

Preconditions

  1. Magento 2.2.5 with Sample Data
  2. php 7.0+

Steps to reproduce

  1. Create a Catalog Rule
  2. Run the cron and indexing
  3. Check /V1/products/{sku} rest api

Expected result

  1. Catalog rule applied price should come in special_price

Actual result

  1. It is not coming.

Original Report: https://github.com/magento/magento2/issues/16511 by @hiteshagrawal84

Confirmed Ready for Work P2 dev in progress Reproduced on 2.4.x S2

All 11 comments

Same here , the rules I applied for the catalog shows in storefront only. It doesn't send special price with products in rest api. Our magento version : 2.2 .Any help ?

Same issue for me. Any update?

Same issue here, is there any update on this?

is this fixed, its too important

Any Updates on that? Maybe there麓s a 3rd party extension for that?

iam wondering why no response here.... this is a MAJOR issue for mobile apps and third parties APIs.
how come this is still neglected till now !

Any updates here? Since its very urgent update to make

This is an important feature for anyone wanting to integrate with 3rd party systems and maintain accurate pricing.

Hi @magento-engcom-team. 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 give me 2.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this


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

    :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

:white_check_mark: Confirmed by @sivaschenko
Thank you for verifying the issue. Based on the provided information internal tickets MC-38622 were created

Issue Available: @sivaschenko, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

@magento I am working on this

Was this page helpful?
0 / 5 - 0 ratings