Transition from non-expiring access token to expiring access token

Authentication & Access
1

Hi everyone,

I’ve developed a few custom apps for a client. These apps don’t require a database because they rely on external APIs. For this reason, I configured everything through environment variables, including the access token, since when I developed them in the past, these tokens theoretically did not expire.

Recently, I noticed that for public apps, access tokens expire after one day and need to be renewed. I know my current app is not affected by this behavior, but I’d like to plan ahead, as I imagine Shopify may eventually introduce a feature that disables non-expiring access tokens for custom apps as well.

So, I’d like to know whether there is a way to continue avoiding the use of a database? maybe using shopify functionality?

I saw that there is an API to get the accessToken every time the problem is that it only works if the app belongs to the same dev dashboard of the store and my apps are in my dev dashboard so this API does not work

2

We do not have any plans to require custom apps to also use expiring tokens. We do recommend using expiring tokens for all apps as a general best practice, but it is not something we plan to enforce for custom apps or merchant created apps.