Executive summary
- What: each app's Settings page in the Dev Dashboard now carries an optional Admin API token expiry switch that enforces expiring tokens ahead of the platform deadline.
- Why: enforcement for existing public apps begins April 1, 2027. Opting in early turns a hard future cutover into a test you control and can reverse.
- Who: app developers and integration owners. Custom apps and merchant-created apps are exempt from the deadline but can still use the switch to rehearse.
What changed
Open an app in the Dev Dashboard, go to Settings, and the Admin API token expiry card now has a Turn on control. Once enabled, the rule applies across every store where that app is installed, not to a single shop of your choosing. GraphQL and REST Admin API requests then fail if they carry a non-expiring offline access token, or a delegate access token with more than 24 hours remaining before it expires. Enforcement can take up to 30 minutes to take effect.
Enabling the setting does not migrate or revoke any existing tokens. It only starts rejecting requests that do not meet the requirements. You can turn it back off if something breaks, though doing so does not move the April 1, 2027 deadline for existing public apps. The Dev Dashboard also highlights potential token expiry problems it has detected in the last 14 days, with detection lagging by roughly a day.
Why it matters
On a Shopify Plus store the storefront is rarely where this bites. The exposure sits in the quiet integrations: nightly ERP syncs, inventory pushes, finance exports, bulk operation pollers. Those run unattended on offline tokens, and a rejected request surfaces days later as missing orders or stale stock rather than as an alert. Rehearsing the failure mode now, on your own calendar, is considerably cheaper than discovering it in a change freeze.
Treat the scope carefully. Because the switch applies to every install, enabling it on a public app is a production change affecting all of your merchants at once. Teams running in-house custom apps have an easier path: fewer installs and a known blast radius.
Role-specific impact
- Marketers: no direct action, but app-dependent features such as loyalty, personalisation and product feed exports can stall silently if a token is rejected. Know which integration owner to call before a campaign depends on one.
- Developers: implement refresh handling, treat authentication failures as a re-auth path rather than a retry loop, and purge long-lived tokens cached in config, secrets stores or job definitions. Exercise background jobs explicitly, not just request-path traffic.
- Store admins: inventory the custom apps and private integrations installed on each store, note which are maintained in-house versus by a vendor, and confirm a named owner for each before 2027 planning.
Use-case example
Real-world scenario
A Plus merchant syncs inventory and orders with NetSuite through a custom app, with a nightly job pushing about 4,000 inventory deltas and a 15 minute order poller. The team cloned the integration into a development app, completed the migration guide, then turned on Admin API token expiry and waited the 30 minutes. Ten of eleven scheduled jobs carried on without issue. The eleventh, a quarterly catalogue export written two years earlier, was still reading a non-expiring token from an environment variable and failed immediately. Finding that in a 30 minute controlled window cost an afternoon. Finding it during the first week of April 2027 would have cost a reconciliation cycle.
Implementation checklist
- Inventory every app and script holding an Admin API token, including delegate tokens issued to internal services.
- Work through the migration guide for each one, then review your app's GraphQL and REST logs plus the Dev Dashboard's 14 day token expiry flags.
- Rehearse on a development app before touching anything merchants depend on, since the setting applies to all installs.
- Turn the setting on in a low-traffic window and allow up to 30 minutes for enforcement to propagate.
- Deliberately trigger background jobs, webhook handlers and retry paths, then check logs for rejected requests.
- Keep the off switch in your rollback plan, and re-test well ahead of April 1, 2027 rather than treating one clean pass as finished.
FAQ
Q: Does the April 2027 deadline apply to our custom app?
A: No. Enforcement covers existing public apps. Custom apps and apps a merchant builds for their own store are excluded, but they can still opt in to validate behaviour.
Q: Can we enable this on one store to limit the risk?
A: Not directly. The setting is per app and takes effect everywhere that app is installed. The equivalent of a single-store test is a separate development app running the same code.
Resources
Admin API token expiry migration guide
Need guidance? Talk to Makro.