The latest Shopify API update is really disappointing. It introduced many unnecessary limitations. Three days ago, I tried to publish an article to my blog and followed the documentation exactly. After contacting support and doing everything they suggested, I was finally told that I need an Admin API key—which has already been removed. I hope Shopify resolves this mistake quickly.
Topic summary
Main issue: A recent Shopify API update introduced new limitations that prevent publishing a blog article via API. Despite following the documentation and trying support’s guidance, the user was told an Admin API key is required—yet that key type has already been removed.
Impact and status: This creates a documentation mismatch and a blocking workflow with no provided workaround. The user calls it a mistake and asks for a quick fix. No resolution or official clarification on whether the removal was intentional; discussion remains open.
Hi @user4489
I completely understand the frustration. API shifts can feel like they are breaking your workflow just for the sake of it, especially when you are trying to handle a simple task like publishing a blog post.
Regarding the Admin API key, there might be a bit of a terminology mix-up from support. Shopify didn’t remove the Admin API, but they did retire the legacy “Private Apps” system in favor of “Custom Apps.” Instead of the old API key and password combination, you now use Admin API access tokens.
If you are trying to publish an article via the API, make sure your Custom App has the write_content scope enabled. Without that specific permission, the API will reject your request regardless of how correct your code is.
Hope this helps!
i do all those steps creat app and scope enabled. but same secret token not enoph for this action
That helps clarify it, thanks for confirming.
If the token and scopes are correct and you’re still getting that error, then it’s usually not the token itself, but how the request is being made. A few things worth double-checking that commonly cause this exact issue:
Make sure you’re using the Admin API access token in the X-Shopify-Access-Token header (not the app secret or client secret).
Confirm the request is hitting the Admin REST API or Admin GraphQL API, not the Storefront API.
Verify the API version in the endpoint (for example /admin/api/2024-10/…). Using an unsupported or mismatched version can silently fail permissions.
For blog articles specifically, ensure you’re publishing to a blog that exists and that you’re passing published: true (REST) or the correct publish mutation (GraphQL).
If you’re still blocked after that, feel free to share the endpoint you’re calling (minus the token) and the exact error message Shopify returns. Happy to take a closer look and help you pinpoint where it’s breaking.
great now we are the whole problime is that there no “Admin API access“ i just see app secret or client secret i already contact with support he told me how i can get it step by step but there is no admin key : i try to many time with defernt store is you can chek from your side i will be happy
1 Like
Yes, I to am going bonkers over this. I have three sites and can not find the shpat.. key at all. I am only getting the shpss… its not showing it when I install the custom app. I’m sure I am missing something but I’ve been at it for 2 days now.