error: Publishable API key required in the request header: x-publishable-api-key. You can manage y | Medusa Community | Page 1

true crane Mar 8, 2025, 3:57 PM

#

I upgraded from medusa 2.1.0 to 2.6.0 and now i get in my nextjs frontend

http:    OPTIONS /store/products?region_id=reg_01XXXXXXXXXXXXXXXXXXx ← http://localhost:3000/ (400) - 3.330 ms
error:   Publishable API key required in the request header: x-publishable-api-key. You can manage your keys in settings in the dashboard.
MedusaError: Publishable API key required in the request header: x-publishable-api-key. You can manage your keys in settings in the dashboard.

did the sdk change or something? I'm confident my key is correct and the same nextjs config works on 2.1.0

warped cairn Mar 11, 2025, 4:54 PM

#

not sure if you updated your store front, iirc think there was a publishable key requirement in one of the releases along the way from 2.1.0 to 2.6.0

https://github.com/medusajs/nextjs-starter-medusa/commit/48d1a7f86d4e8f0e02121f6b6c782bad47a32893

GitHub

Merge pull request #365 from medusajs/feat/publishable-key · medusa...

feat: require publishable keys to run store endpoints

#

ah nvm might be this, try upgrading to 2.6.1

https://github.com/medusajs/medusa/pull/11765/files

GitHub

Fix(framework): http cors middleware order and options by adrien2p ...

FIXES SUP-1101
also fixes #11743
What
The store cors is currently applied after the ensure publishable API key middleware, in this pr the order is fixed and the cors will be applied first.

tall urchin Mar 13, 2025, 7:34 AM

#

Edit: yeah came across the same issue rolled back to 2.5.1 works fine.

#error: Publishable API key required in the request header: x-publishable-api-key. You can manage y