No announcement yet.

Update Product Access Denied error

  • Filter
  • Time
  • Show
Clear All
new posts

    Update Product Access Denied error

    Hi ,

    We are trying to test the product update first via postman.
    We are sending this request below to see if the product quantity will be updated. However, we keep receiving an access denied error


    "Store_Code": "MSP",
    "Function": "Product_Update",

    "Product_SKU": "100-B-740001C",
    "Product_Inventory": 1


    "success": 0,
    "error_code": "access_denied",
    "error_message": "Access denied"

    Based on MIVA documentation
    an access denied error could be for any of the following reasons:
    • Invalid Access Token
    • Missing Header Type or Type mismatch
    • Invalid Content Type
    • IP address is not whitelisted
    • Access Token does not have sufficient privileges
    For reference Miva Docs: Getting Started | Miva JSON API
    We ruled out the underlined reasons since we can get a successful response when we are using other operations, particularly if we are only getting/loading record information from MIVA.

    We have figured out that the token need to have the function Product_Update since it was not yet added before. After adding the Product_Update
    As you can see in this link we are still encountering the issue of access denied.
    Any insight or help will do. Thanks!

    Thanks a lot!

    The most common reason I see for this has to do with the IP address whitelist. To see if this is the case, try whitelisting all IPs temporarily to see if it gets you past this error by adding this to your API token:,::/0

    That will whitelist all IP v4 and v6 IPs. If that does work you'll want to track down the correct IP range vs leaving it available for all IPs
    Brennan Heyde
    VP Product
    Miva, Inc.
    [email protected]


      Hi Brennan,

      I'll ask the MIVA admin to do this on their end. I'll keep this post updated. Thanks!


        Hi Brennan,

        Unfortunately, even though they have whitelisted my IP address it is still throwing the same error message. Please see here Any thoughts?



          In case you didn't know, Miva stores have one IP address for incoming requests, and another one for outgoing. If you determined the requesting store's IP address by looking at the Domain Settings admin page, you've got the incoming address.

          I've run into this problem a couple of times. The IP address for outgoing traffic isn't displayed anywhere that users can get to; you need to ask Support to tell you what it is.

          HTH --
          Kent Multer
          Magic Metal Productions

          * Web developer/designer
          * E-commerce and Miva
          * Author, The Official Miva Web Scripting Book -- available on-line: