Fix & troubleshoot

Fix: Shopify "access token invalid" or store won't connect

When you connect a Shopify store to wptaskify and see "Shopify rejected the access token," "access token invalid/expired," a 401, or "Enter your .myshopify.com store domain," it almost always comes down to one of these: (1) you pasted the wrong kind of token. wptaskify uses the Shopify Admin API token (the value that starts with shpat_), sent as the X-Shopify-Access-Token header. A Storefront API token, an API key, or an API secret key will all be rejected. (2) The store domain is wrong. wptaskify needs the raw myshopify.com domain (e.g. my-store.myshopify.com), not your custom/branded domain (e.g. www.mystore.com) and not a full checkout URL. (3) The token is missing the scopes wptaskify's SEO/content tools need, or belongs to a different custom app than the one you copied from. (4) The token was revoked or the custom app was uninstalled/reinstalled, which invalidates the old token. Note: wptaskify's main Shopify connect is one-click "Install" OAuth, where Shopify hands wptaskify the token automatically and there is nothing to paste. You only deal with a raw token on the manual "add store with domain + Admin API token" path, so most token-format errors happen there.</cause> <parameter name="is_platform_limitation">false

The fix

Step by step

Confirm which connect method you are usingwptaskify has two ways to connect a Shopify store. The recommended one is one-click Install: in the dashboard under Add site, choose Shopify, type your store's myshopify.com domain, click Install on Shopify, review the permissions on Shopify's screen, and click Install. Shopify then sends you back and the token is handled for you, so there is no token to copy. If you used that flow and it worked, you do not need a manual token at all. Only use the manual domain + Admin API token path if the one-click Install is not available to you (it is being rolled out) or you were specifically asked to paste a token.
Use the myshopify.com domain, not your custom domainwptaskify validates the store against its myshopify.com address. Enter it as my-store.myshopify.com (all lowercase, no https://, no trailing slash, no /admin). Do not enter your branded domain like www.yourbrand.com, and do not paste a full page or checkout URL. If you are not sure of the myshopify.com handle, you can see it in your Shopify admin URL (admin.shopify.com/store/<your-handle>) — the domain is <your-handle>.myshopify.com.
Create or open a custom app in Shopify adminIn Shopify admin go to Settings, then Apps and sales channels, then Develop apps (you may first need to click Allow custom app development). Create a new app (give it a name like 'wptaskify'), or open the existing one you made for wptaskify. Important: make sure you are looking at the SAME app you will copy the token from — a token from a different app will be rejected as invalid.
Grant the Admin API scopes wptaskify actually usesIn the app, open Configuration and click Configure Admin API scopes. wptaskify's Shopify tools do products, collections, pages/blogs/articles, discounts (price rules) and theme SEO — so enable read and write for products, read and write for content, read and write for price rules (discounts), read and write for themes, and read for locations. wptaskify does NOT need and does not request orders, customers or inventory scopes, so you can leave those off. Save the scopes. Note: Shopify treats scopes as semi-permanent — if you add a scope later you must re-release the app and reinstall it before the new permission takes effect.
Install the app and copy the Admin API access token (shown once)Open the API credentials tab and click Install app, then confirm. Under 'Admin API access token' click Reveal token once and copy the value that begins with shpat_. Shopify shows this token only one time — if you close or navigate away before copying it, you cannot see it again and must uninstall and reinstall the app to generate a fresh one. Copy the Admin API access token specifically — NOT the API key and NOT the API secret key, and NOT any Storefront API token. Those are different values and wptaskify will reject them.
Paste the domain and token back into wptaskifyReturn to the wptaskify dashboard, open Add site / Shopify (manual option), paste the myshopify.com domain and the shpat_ token, and save. wptaskify validates it immediately by calling Shopify's Admin API; if the domain and token are correct it saves and encrypts the token and your store appears under My Sites. If it still says the token was rejected, re-copy the token (a stray space or a partial copy is a common cause) or generate a new one by reinstalling the app.
If a store that used to work suddenly says 401 / reconnectIf tools were working and now return 'Shopify rejected the access token (401). Reconnect the store,' the token was revoked or the custom app was uninstalled/reinstalled (which invalidates the old token), or someone changed the app's scopes. Fix it by generating a fresh Admin API token (reinstall the custom app to reveal a new shpat_) and reconnecting the store in wptaskify, or by removing and re-adding the store via one-click Install so Shopify issues a new token automatically.
Still stuck? If the token is confirmed to be an Admin API token (shpat_), the domain is the correct myshopify.com address, the scopes are set as above, and wptaskify still rejects it, generate one more fresh token by uninstalling and reinstalling the custom app (this rules out a silently revoked or truncated token) and reconnect. If it still fails, use wptaskify's one-click Shopify Install instead of the manual token — that removes token-copy mistakes entirely by letting Shopify issue the token directly. If neither works, contact wptaskify support with your myshopify.com domain and the exact error text shown (do not send the token itself); a persistent rejection after a fresh token usually points to an account or scope-drift issue support can check on their side.</if_still_stuck> <parameter name="cause">When you connect a Shopify store to wptaskify and see "Shopify rejected the access token," "access token invalid/expired," a 401, or "Enter your .myshopify.com store domain," it almost always comes down to one of these: (1) you pasted the wrong kind of token. wptaskify uses the Shopify Admin API token (the value that starts with shpat_), sent as the X-Shopify-Access-Token header. A Storefront API token, an API key, or an API secret key will all be rejected. (2) The store domain is wrong. wptaskify needs the raw myshopify.com domain (e.g. my-store.myshopify.com), not your custom/branded domain (e.g. www.mystore.com) and not a full checkout URL. (3) The token is missing the scopes wptaskify's SEO/content tools need, or belongs to a different custom app than the one you copied from. (4) The token was revoked or the custom app was uninstalled/reinstalled, which invalidates the old token. Note: wptaskify's main Shopify connect is one-click "Install" OAuth, where Shopify hands wptaskify the token automatically and there is nothing to paste. You only deal with a raw token on the manual "add store with domain + Admin API token" path, so most token-format errors happen there.
FAQ

Related questions

What is the difference between the Admin API token and the Storefront token?

The Admin API access token (starts with shpat_) lets an app read and write your store's back office — products, collections, pages, blogs, discounts and theme content. The Storefront API token is a public, read-mostly token for building custom shopfronts and is sent in a different header. wptaskify needs the Admin API token; a Storefront token, an API key or an API secret key will all be rejected as invalid.

Do I have to give wptaskify access to my orders and customers?

No. wptaskify's Shopify connection is scoped for SEO and content work — products, collections, pages, blogs, discounts (price rules) and theme SEO, plus read access to store locations. It does not request or need orders, customers or inventory permissions on Shopify. (Those are only available on WooCommerce, which connects separately.) You can safely leave order and customer scopes unchecked.

Why does wptaskify reject my custom domain like www.mystore.com?

Shopify's Admin API is addressed by the store's permanent myshopify.com handle, not by your branded domain. wptaskify checks for a .myshopify.com address, so entering a custom domain or a full URL fails. Use the my-store.myshopify.com form — your branded domain still works normally for your shoppers.

I lost the token after installing the app. Can I see it again?

No. Shopify reveals a custom app's Admin API access token only once, right after you install the app. If you did not copy it, you cannot view it again — uninstall and reinstall the app in Settings > Apps > Develop apps to generate a brand-new token (this also creates a new API key and secret), then paste the new token into wptaskify.

Is the one-click Install available to me, or do I have to paste a token?

wptaskify's one-click Shopify Install (no token to copy) is the primary method and is being rolled out; while it is in limited/beta access you may see a 'coming soon' state, in which case the manual domain + Admin API token path is how you connect. Both connect the same way under the hood and both encrypt the token at rest — if one-click Install is available to you, prefer it, since Shopify issues and renews the token for you.

Ready to connect your AI to your site?

Start free How it works