You can now turn on Admin API token expiry from your app’s Settings page in the Dev Dashboard. This optional setting lets you test your migration to expiring Admin API tokens before enforcement begins for existing public apps on April 1, 2027.
What changed
When you enable Admin API token expiry for an app, it applies across every store where that app is installed. GraphQL and REST Admin API requests then fail if they use either:
- A non‑expiring offline access token
- A delegate access token with more than 24 hours remaining before expiry
Enforcement can take up to 30 minutes to take effect. Enabling the setting doesn’t migrate or revoke existing tokens.
You can turn the setting off if you encounter issues. Turning it off doesn’t change the April 1, 2027 enforcement deadline for public apps. That deadline doesn’t apply to custom apps or apps created by merchants.
Who’s affected
This setting is available for all app types in the Dev Dashboard. It affects an app only after you turn it on for that app.
The April 1, 2027 enforcement deadline applies to existing public apps. It doesn’t apply to custom apps or apps that merchants create for their own stores, although those apps can still use this setting to test their behavior with expiring tokens.
What to do
You don’t have to turn on Admin API token expiry. Public apps must still meet the existing migration deadlines described in the migration guide.
If you want to validate your migration early, you can:
- Complete your migration using the Admin API token expiry migration guide, then review your app’s GraphQL and REST logs for affected requests. The Dev Dashboard highlights potential token‑expiry issues detected in the last 14 days, though detection can lag by a day.
- Open your app in the Dev Dashboard, go to Settings, and select Turn on in the Admin API token expiry card. Confirm that you understand that requests that don’t meet token‑expiry requirements will fail.
- Allow up to 30 minutes for enforcement to take effect. Then check your app’s workflows and logs for rejected requests, including requests from background jobs, to confirm that your app handles expiring tokens correctly.