Main issue: Recent Shopify API changes mean newly generated credentials (e.g., prefixes shpss) don’t work with integrations expecting old private app passwords (prefix shppa), leading to “invalid API / Username credentials.”
Context/update: Shopify deprecated Basic HTTP authentication in January 2022, so using API key/password in the URL or Basic Auth header is no longer supported for Admin API.
Solution provided: Switch to Admin API access tokens (prefix shpat) and include them in requests via the X-Shopify-Access-Token header.
Outcome: Implementing the X-Shopify-Access-Token with shpat resolved the integration errors reported.
Action items:
Status: Resolved with a clear migration path. Links and a code snippet are central to understanding the fix.
I think there’s a recent update on Shopify API for custom App. How can I stick to old version in order to be able to generate API key that begin with **“**shppa” for example API password: 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.
Recently, the API key the system is generating starts with “shpss” e.g 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 which is not working for my integration.
Please any solution to this problem.
Thanks
Following this thread as we do have the same issue. We were using a private app in the past and it was generating a shpaa API key which worked.
We tried using shpss and the master API key starting with shpat. No result. We keep on getting “invalid API / Username credentials” error
Looks like they deprecated basic HTTP authentication in January 2022
We solved this issue like this:
You simply need to edit the header and use the master API Access token shpat(which is revealed once) and then add -H 'X-Shopify-Access-Token to the header.
https://{shop}.myshopify.com/admin/api/2022-01/products.json
-H ‘Content-Type: application/json’
-H ‘X-Shopify-Access-Token: {Master_API_access_token}’