What happens to a public Shopify app without an IP allowlist? From 20 November 2026, 11:59 PM ET, Shopify delists it from the App Store, blocks new installs and flags it to merchants in Settings > Apps, while stores that already use it keep working. Shopify relists the app automatically once you turn on an allowlist in the Dev Dashboard. Two dates are still ahead: merchants see a warning from 15 January 2027, and Shopify rejects the app’s Admin API requests from 1 April 2027.
The allowlist names the IP addresses, or the hosting networks (ASNs), that your app’s Admin API requests come from. It is there for leaked access tokens: a token copied out of a log or a compromised dependency works from any machine, and with enforcement on, Shopify rejects it with a 403 anywhere outside the networks you list. This guide covers what a delisted app does now, the dates left, the setup, static IPs or an ASN, where common hosts publish their outbound addresses, and what breaks when the list is wrong.
What happens to an app that missed November 20?
It leaves the Shopify App Store and new merchants can’t install it, but nothing changes yet for the stores that already have it. Merchants can see each installed app’s security setup in Settings > Apps, whether it uses expiring tokens and an IP allowlist, and an app without an allowlist is flagged there.
For apps that are delisted, we’ll relist apps automatically once they add an IP allowlist.
So the way back is the setup below, with enforcement on. There is no form to fill in and no new review. Don’t confuse a delisting with Remove from App Store, which Shopify added to the Partner Dashboard on 12 November for developers who sunset an app: that removal can’t be undone, and listing the app again means submitting it as a new app.
Bulk operations follow their own rules. Shopify began refusing bulk queries and bulk mutations from public apps without an allowlist on 12 November, and since 6 November an app created by a partner also needs bulk operations enabled before it can run them. Shopify enabled them for apps that already ran bulk operations. The two are separate, so an app with an allowlist can still be refused if bulk queries or bulk mutations aren’t enabled, or if it hasn’t started one in 31 days and lost the access. You enable them under Access requests in your app’s settings, as Shopify's bulk operations guide explains.
The dates still ahead
The requirement covers every public app that calls the Admin API, and every custom app installed on a store outside the organization that owns it. The two kinds of app follow different calendars.
Custom apps installed only on stores in your own organization are not covered, and neither are apps a merchant creates in the Dev Dashboard or in the Shopify admin. Since 17 November, custom apps created in the Shopify admin appear in the Dev Dashboard too, where you can give them an allowlist even though none is required. If your app makes Admin API calls from a merchant’s own infrastructure, Shopify asks you to move away from that design and accepts requests for an extension.
Two other requirements run alongside on Shopify’s list of upcoming security deadlines. They cover expiring offline access tokens, and the network access that apps running code on the online store must declare in shopify.app.toml. Answer for your app to see which dates apply to it.
Which dates apply to your app?
Answer for one app that calls the Admin API from its servers, the case Shopify’s IP allowlist requirement names. The list shows the Shopify security dates that apply to it, with what to do.
Dates for a public app, no IP allowlist, no bulk operations, no code on the online store, expiring offline tokens:
- 20 November 2026IP allowlistDelisted from the App Store, blocked from new installs and flagged in merchants' Settings > Apps. Existing installs keep working. Turn on the allowlist to be relisted.
- 15 January 2027IP allowlistMerchants who use the app see a warning in the Shopify admin.
- 1 April 2027IP allowlistShopify rejects the app's GraphQL and REST Admin API requests.
Setting up the allowlist in the Dev Dashboard
The allowlist lives in your app’s settings in the Dev Dashboard, and each app has its own. Shopify lets you build the list, test it against your real traffic, and only then enforce it.
- Open your app in the Dev Dashboard, select Settings, then Manage in the IP allowlist section.
- Enter your addresses under IP addresses or CIDR ranges, one per line, your ASNs under Networks (ASN), or both. If you enter ASNs, choose the countries your app runs in under Limit ASNs to countries.
- Under Test against recent traffic, select Run test. It checks your app’s requests of the last 30 days against the list. Recent requests can take a few minutes to show up.
- When none of your own requests would be blocked, turn on Enforce IP allowlist and select Save.
- Make a GraphQL Admin API request from a machine outside the list and check that it fails with a
403.
Turning Enforce IP allowlist off again keeps the list, so you can switch it back on later.
Try it on a staging app first. Enforcement applies to every store the app is installed on, so try it on a separate copy of your app, with its own client ID, installed on a development store and served by the same infrastructure. Requests made through a dev preview (shopify app dev) are never rejected, so they prove nothing.
Is it the same as network access in shopify.app.toml?
No. The IP allowlist is set only in the Dev Dashboard and controls where your app’s Admin API requests may come from. The [network_access] section of shopify.app.toml covers the opposite direction: what your app’s code loads or links to from storefront, checkout and Shopify admin pages.
allowed_sourceslists the HTTPS origins your extensions, app home and app proxy pages load from or send requests to. Shopify now requires it for apps that run code on the online store (a theme app extension, script tags, an app proxy, thewrite_themesscope, or a web pixel withwrite_open_pixels). An empty list counts as a declaration.allowed_navigation_hostslists the external hosts your app links customers to, which then skip Shopify’s exit warning. It stays optional.
The network access testing preview on development stores checks those lists and only warns. Neither setting replaces the other.
Static IPs or an ASN?
Use static IP addresses whenever your host can give you some, and an ASN only for requests that leave from addresses that change. An address list is the narrowest allowlist: only machines at those addresses can use your tokens, which means only your own servers when the addresses are dedicated to you. Some hosts share their static addresses with a few other customers (see the table below), which is still far narrower than an ASN, since an ASN admits every machine on that provider’s network.
Anyone who runs servers in an ASN that you allow, and who has a stolen token, can use it from there. Allowlist only IP addresses when you can, and if you allowlist ASNs, then list only the countries your app runs in.
One allowlist can hold both, so you don’t have to choose: your servers’ static addresses as IPs, and a serverless function or a third-party tool that uses your app’s tokens as an ASN, or as its own single address when the tool publishes one. A request that matches either is allowed.
Enter addresses as CIDR ranges that start at their network address (203.0.113.0/24, not 203.0.113.7/24), public addresses only. Behind a NAT gateway, list the gateway’s addresses, and if your servers reach Shopify over IPv6, add their IPv6 addresses too. A country under Limit ASNs to countries is where the GeoLite data places the address, not where the provider is registered.
To find which ASN your requests come from, open your app’s Logs in the Dev Dashboard: every GraphQL and REST request entry shows its Client IP. Look those addresses up, and check your host’s documentation, because a provider can run several ASNs and add more over time.
Finding your outbound IPs on each host
Most hosts don’t give an app fixed outbound addresses by default. Some sell or include them as an option, and some publish only their address ranges. The table sums up what each vendor documents.
gcloud compute addresses list. Google's guidefly ips allocate-egress, read with fly ips list, and allow both addresses of each pair. Fly.io's docsheroku spaces:info. For an add-on, its own documentation. Heroku's helpapp_get). Meridian’s docsOn Vercel’s plans without Static IPs, on Railway below Pro, and on Heroku’s Common Runtime without an add-on, there is no fixed address to list, so an ASN limited to your countries is the only option. Heroku itself advises against opening a firewall to a whole AWS region, which is what its published ranges amount to. Render’s shared regional ranges are narrower than an ASN, though every other service in the region shares them.
If you do allow an ASN, take it from your own logs rather than from a list. Of these vendors, only Google (15169 as its primary ASN) and Amazon (16509 and 14618) name their ASNs in their documentation, and neither ties a product’s outbound traffic to one of them. The Client IPs in your Dev Dashboard logs tell you which networks your requests really leave from.
Allowlisting an app hosted on Meridian
Every app hosted on Meridian calls the internet from a fixed, published set of IP addresses, the same for all of its environments. Open Hosting, Settings, find the Outbound IPs card under Networking, select Copy all and paste the list into the Dev Dashboard, with the addresses of anything else that calls the Admin API with your app’s tokens.
- Allow every address on the list, including the two tagged Meridian platform. Meridian uses them for its own Admin API calls with your app’s token, such as Plan Builder billing and registering webhooks. Without them, Shopify refuses those calls once you enforce.
- Enforce only once every environment that uses this Shopify app shows Applied since on the card. One still marked Waiting for deploy calls from Google’s shared range until its next deploy, so its first Admin API call after you enforce would get a
403. In Run test, a blocked request from Google’s range dated before an environment’s Applied since is that old traffic. Check any other blocked address before you enforce: it may be a worker or a tool that hasn’t called since. - The addresses are shared with the other apps Meridian hosts in the same region. A leaked token still works from them and from anything else on your allowlist, but from nowhere else. That is far narrower than allowing Google Cloud’s ASN, though not a guarantee against another app on Meridian.
The Outbound IPs documentation covers local development, long-lived connections and how Meridian announces an address before any call leaves from it.
What breaks when the allowlist is wrong
With enforcement on, any Admin API request from outside the list fails with a 403, and so does a request whose source address Shopify can’t confirm. The usual causes are callers you forgot:
- Background workers, cron jobs and queue consumers that run on another service than your web server.
- Webhook handlers that call back into the Admin API from a serverless function or an edge runtime.
- Third-party tools, scripts or support consoles that use your app’s tokens. Add their addresses or their ASN.
- Your own computer. Outside a dev preview on a development store, local scripts against an app that enforces its allowlist are refused. Keep a separate Shopify app for development rather than adding a home or office address to the production list.
Two kinds of request can’t work with an allowlist at all, because Shopify can’t confirm where they come from: the Shopify Flow Send HTTP request action using your app’s token, and GraphQL Admin API requests from a storefront hosted on Oxygen. Others are never rejected: dev preview requests on development stores, and Direct API access from your app’s embedded pages and POS UI extensions, which run in the merchant’s browser or device.
For bulk operations, developers on Shopify's community board report this GraphQL error from an app without an allowlist, with the code ACCESS_DENIED: Bulk operations require IP restrictions. Turn on IP restrictions for this app to run bulk operations. Shopify’s documentation doesn’t quote the message.
A 403 has other causes too, such as a store marked as fraudulent, so check the request’s Client IP in the Dev Dashboard logs before you change the list. Shopify recommends alerting on 403 responses from your own servers, since one usually means an address you forgot to list. Check its cause before you change the list.
In Run test results, sort the addresses that would be blocked into three groups. Your own servers go on the list. Requests from before you moved to fixed addresses are old traffic and won’t come back, so compare their dates with the day you switched. An address you can’t place at all deserves a closer look before you enforce, because a token used from somewhere unknown is exactly what the allowlist is there to stop.
A checklist before you turn on enforcement
- List every place that calls the Admin API with your app’s tokens: web servers, workers, cron jobs, functions, third-party tools.
- Get fixed outbound addresses where your host offers them, or note the host’s ASNs and regions.
- Read the Client IP column of your Dev Dashboard logs to catch callers you missed.
- Enter addresses first, ASNs only for what remains, limited to your countries.
- Run the test, and explain every address that would be blocked.
- Turn on Enforce IP allowlist, save, and confirm a request from outside the list gets a 403.
- If your app runs bulk operations, check that bulk queries and bulk mutations are enabled.
- Repeat for every Shopify app you run, staging and development apps included.
- Alert on 403 responses from your own servers.
Sources: Shopify’s IP allowlist setup guide, Restrict API access to your IP addresses, About app security, Monitoring and logs, Declare your app's network access and the bulk operations guide, and its changelog entries Restrict Admin API access with an IP allowlist and network access rules in shopify.app.toml (27 October 2026), network access testing on dev stores (4 November), IP allowlists required for public apps, ASN support for serverless hosting and App security updates (5 November), enabling bulk operations (6 November), IP allowlists required for custom apps and IP addresses and ASNs together (11 November), Remove your app from the Shopify App Store yourself (12 November) and App security updates: what's required next (14 November). Each host’s own documentation is linked in the table. All checked on 19 November 2026. Shopify has changed these rules several times in a few weeks, so check its guide before you enforce.

