{"section":"known-issues","requestedLocale":"en","requestedSlug":"pricing-api-allows-negative-values","locale":"en","slug":"pricing-api-allows-negative-values","path":"docs/en/known-issues/Catalog/pricing-api-allows-negative-values.md","branch":"main","content":"## Summary\n\n\nCurrently, the PUT Price API allows the input of negative values via PUT API Payload, if you set the markup and baseprice to negative values, you'll set the product as unavailable.\n\n\n\n\n##\n\n## Simulation\n\n\nOn the API https://api.vtex.com/account/pricing/prices/1\n\nSet the following price:\n\n`{`\n`  \"itemId\": \"1\",`\n`  \"listPrice\": null,`\n`  \"costPrice\": 11.9,`\n`  \"markup\": -100,`\n`  \"basePrice\": null,`\n`  \"fixedPrices\": [ ]`\n`}`\n\nThe response will be:\n\n ![](https://raw.githubusercontent.com/vtexdocs/known-issues/refs/heads/main/docs/en/known-issues/Catalog/pricing-api-allows-negative-values_1.png)\n\nWhich breaks the pricing logic and makes the product unavailable, since the checkout and catalog applications aren't able to deal with negative price values.\n\n\n\n##\n\n## Workaround\n\n\nn/a"}