@Tommy Kenton GET api route is cached by default in production

Im new how can I fix this?

Simply change GET to POST if it's okay

But then how do I GET something?

This worked would you recommend noStore or cookies?

noStore() unless you have something with cookie()

but I believe your real api is not gonna be only for getting random number, right?

you might end up using POST or reading cookie

still not, then noStore

Yes, I'm going to try make auth.

Then you probably need cookie(), right?

I'm not sure, I guess to store a user token or something?

store token? it should be from cookie or header, right?

if you use next/headers your api route will be fully dynamic even if it's GET` - so you won't need noStore()

@James4u, could you tell me if I'm experiencing the same problem? What's the best way to maintain GET?
https://nextjs-forum.com/post/1265350493585281156

@Lucas Bonafé your issue is not related to the cache I guess?

but I have a tip for you, you can run npm run start instead of npm run dev to run production server on your local.

I've already tested with npm run dev and vercel dev, I just tested with npm run build and npm run start now and it worked normally, I'll try to configure the Vercel key without an escape in the $ that the ASAAS_API_KEY variable has...

Same error...

I have not yet tested the solutions described in the cache

Edit: Tested and not work...