Admin API / Dev Dashboard / Optional setting

Admin API token expiry
Turn it on yourself and test "before it's enforced in production"

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.

What's on this page
  1. What's actually changing (30-second overview)
  2. How it works: How requests are handled after you turn it on
  3. Rejected tokens vs. accepted tokens
  4. Affected apps and the April 1, 2027 deadline
  5. Timeline
  6. How to test early (3 steps)
  7. 5 key points for developers
  8. 3 business use cases
  9. One-line summary for proposals

1What's actually changing

For existing public apps, starting April 1, 2027,expiring Admin API tokens become mandatory.
Now you can turn that enforcement mode on early, at your option, in the Dev Dashboard app settings , so you can confirm your migration is correct before the production deadline.
Testing in production

Before: No way to see production behavior until the deadline

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.

Now: Test enforcement on your own schedule

Click Turn on in the "Admin API token expiry" card in Settings. If something goes wrong, you can turn it back off.

2How it works: How requests are handled after you turn it on

Dev Dashboard Settings > Admin API token expiry Turned on per app Up to 30 minutes All installed stores GraphQL / REST Admin API Per-store toggling not mentioned Token Result Accepted Expiring tokens that meet the requirements Fails • Non-expiring offline tokens Over 24h left on delegate tokens
The setting is turned on per appand applies to all storeswhere that app is installed. Changes can take up to 30 minutesto take effect.
Turning it on does not migrate or revoke existing tokens(it only makes requests with non-compliant tokens fail).

3Rejected tokens / accepted tokens

Requests that fail when enabled

Fails

Non-expiring offline access tokens

Traditional offline tokens that can be used indefinitely.

Fails >24h

Delegate access tokens with more than 24 hours until expiry

Delegate tokens must have 24 hours or less of remaining validity.

Applies to both the GraphQL and REST Admin APIs. This article doesn't cover the error codes or response format on failure.

4Eligible apps and the April 1, 2027 deadline

App typeCan 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)
This setting is optional. You don't have to turn it on, but public apps must still meet the existing migration deadline set out in the migration guide.

5Timeline

Now 2026/11/16 Early opt-in available A window to opt in, verify, and turn it back off if needed 2027/4/1 Enforcement begins for existing public apps

6Early verification steps (3 steps)

1

Complete the migration and check your logs

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).

2

Turn on in Settings

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.

3

Wait 30 minutes and check behavior

It can take up to 30 minutes to take effect. Then check your workflows and logs for rejected requests.Background jobsincluded.

If problems come up, you can turn the setting back off. However, turning it off does not change public apps' April 1, 2027 enforcement deadline.

75 key points for engineers

1. Scope: every store the app is installed on

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.

≤24h

2. Delegate tokens have conditions too

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.

3. 30-minute rollout lag / 1-day detection lag

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.

4. Don't overlook background jobs

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.

ON OFF

5. Turning it on is non-destructive and reversible, but the deadline doesn't move

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.

83 practical use cases

Before April 1, 2027
USE CASE 1

Public apps: a dry run before the deadline

Challenge
You run a public app, but you can't be sure your migration to expiring tokens is truly complete until enforcement begins.
Approach
Implement the changes using the migration guide → check your logs and the highlights in the Dev Dashboard → click Turn on in Settings → monitor rejected requests starting 30 minutes later.
Impact
Eliminate the risk of outages on April 1, 2027 ahead of time. If something breaks, turn it back off and fix it.
Technical notes
The setting applies to every store where the app is installed, so pick a low-impact time window and share the steps to turn it off in advance.
cron batch
USE CASE 2

Finding background processes such as inventory and order sync

Challenge
UI actions work, but you don't have full visibility into which tokens unattended jobs like nightly batches and scheduled syncs are using.
Approach
Turn the setting on for a test app, run your jobs for a while, pull rejected requests from the logs, and fix token retrieval in the affected code paths.
Impact
Catch migration gaps in rarely run processes before enforcement hits production.
Technical notes
Dev Dashboard detection covers the last 14 days and can lag by up to one day. For weekly or monthly jobs, set an observation window that covers their run cycle.
Custom App
USE CASE 3

Testing expiring tokens with custom apps too

Challenge
Client-specific custom apps and merchant-created apps aren't subject to the deadline, but you still want to check how they behave with expiring tokens.
Approach
Turn on the same setting for your custom app and test whether it works with expiring tokens. If there are problems, turn it off.
Impact
Even for apps that aren't subject to enforcement, you can confirm they work with expiring tokens before deciding on your implementation approach.
Technical notes
The April 1, 2027 deadline doesn't apply to custom apps or merchant-created apps (the setting is for testing only). No future enforcement is announced for them.

9One-line summary for proposals

"You can test Admin API expiring-token enforcementby opting in from the Dev Dashboard before it's enforced in production on April 1, 2027 .
Existing tokens keep working, and you can turn it off anytime. Validate your migration now, background jobs included."