Hi @Richard Mockler 

Thanks for reaching out to the Community!

It looks like you have already been added by the Support Specialist you worked with, according to their reply:

After reviewing our system logs a bit more closely, I can confirm that what you’re running into is a known bug with BigCommerce. It seems what happens is our system is inadvertently modifying the store search to look at the wrong API path for V2 instead of V3. We’re not sure the cause just yet.

With that being the case, we’ve filed a bug report with the team in charge of the BigCommerce integration so that they can look into this and hopefully get it resolved.

We can’t provide an exact timeframe of when the developers will resolve this, but we’ll let you know via email.

Let me know if you have other questions.

Thank you for the amazingly quick reply and the detail. I had not heard that so very helpful. 

Hi @Richard Mockler 

You’re welcome.

Let us know if you have other questions, we’ll be happy to help! 

Hi @Charie and @Richard Mockler . Do you know if Zapier can now connect to BigCommerce? I’m also trying to hook up a new connection to BigCommerce and having trouble even though I was able to do it successfully a few months ago.

Hi @LKramer 

Jumping in to see if I can help!

I see it is still an active bug. Besides that I don't have any updates, unfortunately. 

Since this integration is owned by BigCommerce, I am not able to see if they are actively working on it or not. You may want to reach out to their support team as well as hearing about issues from your customer always carries more weight.

I’ve added you to our bug report so that once the issue is fixed, we’ll notify you!

Ok, thank you. This is a different response than I received before, which indicated that the BigCommerce 
team at Zapier was working on it.

Does anyone have any updates to this? Such a large integration would be effected this long. 

Hi there @HelpMeHelpyou,

Unfortunately, we don’t have any updates regarding the bug at the moment. Prioritization is largely dependent on the number of customers affected.

I'm sorry that I don't have a more definitive answer for you right now. But please know that we appreciate your patience and we'll definitely reach out to you via email or on this thread as soon as we have any updates.

Is this still an issue? I have tried with other E-commerce platforms and works with wordpress, woocommerce but not with Bigcommerce. 

Error -

We hit an error adding your new account

authentication failed: The app returned "Not found".

Hey there, @NPM_Hermes! 

Sorry to say there aren’t any updates to share at the moment but I did add you to the list of impacted users. This is the best way to stay informed as it ensures you'll be emailed once a fix is live!  We'll also be sure to keep the thread updated with any news.

Appreciate you reaching out and letting us know!

I had this issue too, until I realized that when connecting to BigCommerce only put the hash from the url, not the full URL.

I urge Zapier staff to make the connection screen more clear.

Thanks so much for reaching out here, @1118m. We really appreciate you taking the time to share this information with the rest of the Community!

I’m so pleased you were able to get this solved by entering the hash, not the full URL when adding the connection to BigCommerce. Hopefully your fix will solve things for other folks being affected by this too! 

Much like others in this thread, we are having the same issue connecting to our Staging BigCommerce store in Zapier via an API endpoint/Access token combination. This was after following the connection steps exactly and replicating the exact configuration of a BigCommerce API endpoint that still is working. We have 3 other Zaps with triggers from our Production BigCommerce store that are still working that were configured earlier this year (mid-January).

We noticed the BigCommerce triggers in the working Zaps are available for update, but are avoiding updating them due to concerns that doing so will bring the bug down and disable the Zaps entirely.

Any updates to the priority or progress on this known bugs would be greatly appreciated.

Hi @ASMBL-Curology!

Sorry to hear you’re also being affected by this issue. I’m unable to share any updates on this at the moment, and it appears our Support team have already added you to the list of folks being impacted by this. This will help to increase it’s priority and allows us to send you an email notification the minute a fix is implemented by the BigCommerce app’s developers. 

I did also want to mention that it should be possible to duplicate your existing Zaps that use BigCommerce and switch the duplicated Zaps to use the latest version of the BigCommerce triggers to see if that resolves the issue - without affecting your existing Zaps. Please do let keep us in the loop on how that goes! 

Like @1118m said above, only put the store hash in the url field. Do not add the full url. So if your url is 

https://api.bigcommerce.com/stores/3rewqfsfaf/v3/ only input 3rewqfsfaf in the field. Then add your access token. 

Thanks for reaching out here, @mathicks. Glad to hear the workaround 118m shared above worked for you! 

I’ve also added you to the list of affected users to help increase it’s priority. There’s no ETA available on when it will be sorted by but we’ll notify you by email as soon as it’s been resolved. 

When creating the API Token in BC, allow “read-only” access to everything under OAuth scopes. If “read-only” isn’t an option, leave it set to “None”.

You also want to make sure the store hash is only the hash, not the full URL.

Thanks for sharing those suggestions here, @AJ_LFOD! The Community appreciates it!  

I can confirm the “read_only” instructions from @AJ_LFOD do indeed work thank goodness. 

Yay! Thanks for confirming that the solution shared by @AJ_LFOD resolved things for you as well, @ec_206!  

Hopefully it’ll work for everyone else running into this issue too! 

@SamB is there documentation somewhere that lists what specific OAuth scopes we’re suppose to set as “read-only”, “modify” etc. in BigCommerce? I couldn’t find anything in Zapier. Even though setting everything to “read-only” works, this doesn’t seem correct. I would think there are particular scopes we need to set as “modify” for only the data we need from BigCommerce (e.g - Orders). Thanks!

Hi @ec_206!

I couldn’t find anything documented internally but looking at BigCommerce’s API documentation it mentions needing to set the scopes as “modify” for and “read-only” like so:


The BigCommerce app on Zapier was built and is maintained by BigCommerce’s developers so it might be worth reaching out to them directly to have that confirmed officially.