Access Token no longer available on Shopify?

[olsp]

I just tried to connect the Shopify Plugin to the Shopify store but can't get the needed credentials.

I created an app via the dev dashboard but can't find the necessary data for

4. Admin API access token: Reveal and copy this value into your .env file, as SHOPIFY_ADMIN_ACCESS_TOKEN.

What I do get via the dev dashboard is Client ID and Secret but no Admin API access token.

From what I understand, the dev dashboard is rather new and also a new API version is available (2025-10). Is the plugin not yet compatible with the changes made by Shopify or am I doing something wrong?

[linear[bot]]

PT-2978

[nfourtythree]

Hi @olsp

Thank you for your message.

When creating your develop app in Shopify your Admin API access token can be retrieved from the API credentials tab.

Shopify have just recently updated their PHP SDK (which this plugin relies on) with 2025-10 compatibility, we are currently testing and updating this plugin with that version.

We hope to get a release out soon, in the meantime you can use the 2025-07 version which the plugin is compatible with and will see no difference in performance.

Hope this helps, thanks!

[olsp]

Hi @nfourtythree,

thanks for looking into this. Unfortunately, I can't see the screen like on your screenshot. I assume you are not under https://dev.shopify.com where new apps are created? It says, that new apps can't be created the "old" way after January 2026. So I don't want to use this option since it's already marked deprecated.

[joshmlamb]

Hi @nfourtythree,

I have also created an app through the dev dashboard and the only API credentials available are Client ID & Secret. In order to have access to the Storefront API, this has to be specifically requested when creating the app, this doesn't return a Storefront API specific token.

[nfourtythree]

Hi all

Just to keep everyone up-to-date we are working on a new version of the plugin which will be compatible with creating apps from the Dev Dashboard.

We are trying to get this out as soon as possible and we will post any updates related to that in this thread.

As a question on this topic, the few test stores we have still show access to creating a custom develop app in the current methodology. Do your stores not show the option to create a legacy app in Settings > Apps and sales channels > Develop App?

Thanks!

[olsp]

Thanks for the update. It seems I could create a legacy app, but I prefer not to. I don't want to start something new that's already "deprecated". Sooner or later I will have to switch to the new system. Since my current project is not super urgent, I prefer to wait until the plugin is compatible with the Dev Dashboard.

Thank you for taking care of this

[olsp]

Hi @nfourtythree. I was wondering if you can provide an update on this issue? Maybe you can even give an outlook on when the new version will be available?

[brettburwell]

Hi @nfourtythree. Gentle, but semi-urgent bump on this.

I have a project in active dev that's blocked from moving forward right now. Hoping this is something that will be resolved soon.

[AugustMiller]

Hey, all—Nathaniel and I have been going back-and-forth about the ideal connection flow, and have published a cursory guide on the 7.x branch.

The new process for getting the app and store connected is straightforward, but not as plug-and-play as a "legacy" app.

(You should be able to follow this guide, but replace the API/webhook version with 2025-07 to maintain compatability with 6.x. When you upgrade, you will need to “release” and new version of your app using 2025-10.)

If you are working with the store owner as a partner organization, you may need to perform an additional setup step, which Shopify calls selecting a distribution. This is done via the partner dashboard.

As far as we’ve been able to tell, there are no store-specific keys or credentials to gather—when a user installs the custom app, you are essentially authorizing it to interact with the store, so all you need is the API key and API secret key from your app, and the store’s domain. The temporary key or "access token" we ultimately use to make requests is generated via a session handshake.

Let us know if you have any trouble getting set up!

[brettburwell]

@AugustMiller Thanks for the thoughtful and detailed response. This is helpful and awesome to hear.

[brettburwell]

@AugustMiller Couple quick (I hope) questions.

I was able to successfully create an app through the Dev Dashboard and have it installed in my Shopify store, but I'm not having luck connecting it to Craft (specifically with creating the webhooks).

With that in mind, a few questions / notes:

1. I'm running Craft 5.8.27 and Shopify 6.1.3. Based on your note above, it sounds like your recommended approach was to stay on the 6.x version, but follow the guide on the 7.x branch. Is that correct (vs. jumping to 7.x to install)?
2. You mentioned that we don't need an "access token", but when I tried adding the other values and saving the plugin settings it errored out with a "Shopify Access Token cannot be blank" message. That makes sense, so I just put in a dummy value. Does that value need to be set to anything specific?
3. In case it's helpful, I'm seeing the same error described here, when trying to create webhooks. I've tried on my local machine and the staging server with no luck.

Any tips or guidance you can offer would be much appreciated! Thanks in advance.

[nfourtythree]

Hi all

We know there are a lot of people eagerly waiting for this update. Rest assured that we are working on this and trying to get something out as soon as possible.

We hit some teething troubles when testing the new integration approach with various types of stores and developer permissions. This has caused us to explore a new route for authenticating your Craft project with the app created in Shopify.

Unfortunately, these issues were not apparent in the first instance and having done some digging it seems, at least to us, that there is some convoluted reasons it works the way it does in Shopify. A number of other developers are also having issues with the process and migrating from the legacy app method to the new one.

We are going through final testing now and hope to get an updated guide/readme to everyone as soon as we can.

Apologies for the delay, and we really appreciate your patience.

Thanks!