On this page
Why an app that worked yesterday may suddenly fail
For years, a valid Admin API token was often enough to make a request from any server. Shopify now adds a network boundary: even a valid token is rejected when used outside approved IP ranges or networks. The practical risk is not only an attacker with a leaked token. It is a legitimate background worker, cron job, queue consumer, serverless function, or bulk-operation caller whose outbound network was missed during setup.
Shopify’s November 5 announcement is a requirement, not merely the optional security advice from earlier tutorials. Its article summary mentions November 11 for bulk ops, but the detailed action requirements and enforcement table say November 12 at 11:59 PM ET. Use the detailed enforcement deadline, and complete the change earlier rather than relying on the last day.
Map the outbound traffic before changing settings
List every environment that calls GraphQL or REST Admin API using the public app’s tokens: production web servers, asynchronous workers, inventory/ERP sync jobs, deployment runners, scheduled tasks, and separate regions. Record the public egress IP or provider network for each. Do not confuse inbound webhook IPs with your own outbound API traffic.
Static infrastructure can use public IP/CIDR entries. For dynamic or serverless hosting, Shopify’s current guidance supports allowlisting hosting-provider networks by autonomous system number (ASN). An ASN covers a broader network than a single server, so review that tradeoff with your infrastructure owner. Do not paste example documentation IP addresses into production.
Enable enforcement without cutting off your own workers
In the Dev Dashboard, open the app’s Settings and the IP allowlist management section. Add the actual addresses or networks, run the recent-traffic test, investigate any legitimate source flagged as blocked, then enable enforcement. Exercise your background jobs after saving. Shopify documents HTTP 403 for Admin API calls from unapproved networks; treat new 403s as a network-policy investigation, not automatically an OAuth or access-scope problem.
Keep token expiry work separate. Shopify’s enforcement schedule also includes expiring offline access tokens, but an IP allowlist does not refresh a token and token rotation does not fix an unapproved network.
What happens if you miss it?
Shopify says bulk queries and mutations from public apps without an allowlist are blocked after November 12. By November 20, affected apps can be delisted from the App Store and lose new installs. Merchant-facing warnings begin January 15, 2027; existing installs’ Admin API calls are scheduled to fail April 1, 2027. Those later dates are not permission to delay the bulk-operation or App Store work.
How to test this
- Identify every service and region making Admin API calls, including bulk workers and cron jobs.
- Use Dev Dashboard’s recent-traffic test; resolve any legitimate source that would be blocked.
- Enable enforcement and verify normal GraphQL reads, writes, bulk query initiation, and bulk mutation initiation from production workers.
- From a controlled, unapproved source, verify a request with an app token returns HTTP 403; do not expose tokens in logs.
- Monitor production 403 rates and review the allowlist after hosting or network changes.

