From your app settings in the Dev Dashboard, you can now enable the mode that requires expiring tokens ahead of time. Enforcement for existing public apps begins April 1, 2027. Until then, you can safely verify that your migration works correctly.
Even if you implemented the migration guide, you couldn't confirm how your app behaved when non-expiring tokens were actually rejected until enforcement began.
Click Turn on in the "Admin API token expiry" card in Settings. If something goes wrong, you can turn it back off.
Traditional offline tokens that can be used indefinitely.
Delegate tokens must have 24 hours or less of remaining validity.
| App type | Can use this setting? | April 1, 2027 enforcement |
|---|---|---|
| Existing public apps | Yes | Applies The deadline applies whether the setting is on or off |
| Custom apps | Yes For testing behavior | Not applicable |
| Apps merchants build for their own store | Yes For testing behavior | Not applicable |
| Apps without the setting turned on | — | No impact (only affects apps that turn it on) |
After implementing the changes in the migration guide, check the relevant requests in your GraphQL / REST logs. The Dev Dashboard highlights potential issues from the last 14 days (detection can lag by up to 1 day).
Open your app in the Dev Dashboard and click "Turn on" on the Settings > Admin API token expiry card. Acknowledge that non-compliant requests will fail, then confirm.
It can take up to 30 minutes to take effect. Then check your workflows and logs for rejected requests.Background jobsincluded.
This is an app-level setting that applies to every store the app is installed on at once. The article doesn't describe any way to test on a subset of stores. Understand the impact before turning it on for a production app.
Not only non-expiring offline tokens, but alsodelegate access tokens with more than 24 hours remaining are rejected. Review any implementation that sets a lifetime when issuing delegate tokens.
Enforcement takes effect up to 30 minutes later, and the Dev Dashboard's issue highlights cover the last 14 days with up to a 1-day delay. Don't conclude there are no issues just because nothing shows up right after turning it on.
The article explicitly says to also check requests from background jobs. Paths that use offline tokens, such as cron jobs, post-webhook processing, and batch syncs, are the main things to check.
Turning it on doesn't migrate or revoke existing tokens, soyou can try it knowing that turning it off restores the original behavior. However, the April 1, 2027 deadline for public apps arrives regardless of this setting.