Shopify public apps need an IP allowlist by November 20. Check bulk ops before the 12th
Shopify made IP allowlists required for every public app on November 5. Bulk Admin API jobs start failing without one on the 12th; App Store listing follows on the 20th. Merchant checklist and builder setup before peak.

Yes: as of November 5, 2026 Shopify requires an IP allowlist on every public app that calls the Admin API. Turn it on by November 20, 2026 at 11:59 PM ET. Bulk queries and mutations from public apps without an allowlist are blocked after November 12, 2026 at 11:59 PM ET. Merchants should open Settings > Apps now, flag apps that lack an allowlist, and ask those developers before Black Friday volume hits. App maintainers enable allowlist in the Dev Dashboard (static IP/CIDR or ASN, not both), test against the last 30 days of traffic, then verify an outside request returns 403.
What changed on November 5
On October 27 Shopify told public-app developers that an IP allowlist was a good idea. On November 5 it stopped being optional.
Shopify's changelog is blunt: IP allowlist is now required for every public app. If your app sits in the App Store, or is otherwise publicly distributed, and it calls the Admin API, the clock is running. Custom and merchant-only apps are a different lane in Shopify's product language; this note sticks to the public-app requirement Shopify stated.
The point of the control is simple. Once the allowlist is on, Admin API tokens only work from the IP addresses or networks you listed. A token that leaks out of a log, a chat paste, or a compromised laptop cannot be used from somewhere else. That is the whole security story Shopify is selling, and it is a good one if you finish the setup before enforcement starts cutting into holiday ops.
Two dates matter first. Bulk operations need the allowlist by November 12, 2026 at 11:59 PM Eastern. Everything else for public Admin API callers needs it by November 20, 2026 at 11:59 PM Eastern. Peak season does not care that your vendor is on vacation.
Read the enforcement calendar once
Shopify published a stepped calendar for the IP allowlist. Treat it as a work plan, not a rumor mill.
November 12, 2026. Bulk queries and mutations from public apps without an allowlist are blocked. If an app runs catalog syncs, inventory dumps, order exports, or any other bulk Admin API job for you, this is the first day it can go quiet.
November 20, 2026. Public apps without an allowlist are delisted from the App Store and blocked from new installs. Merchants also start seeing those apps flagged in Settings > Apps.
January 15, 2027. Merchants see a warning in admin for apps still missing the allowlist.
April 1, 2027. Admin API requests from those apps fail. Existing installs keep working until that date, on the same track as Shopify's expiring offline tokens work.
So: bulk breaks first, discovery and new installs break next, and the hard API cut comes in April. If you only remember two numbers before Black Friday week, remember the 12th and the 20th.
Sequence of work
Shopify IP allowlist enforcement dates
- Nov 5, 2026
IP allowlist required for every public app (was recommended Oct 27).
- Nov 12, 2026 · 11:59 PM ET
Bulk queries and mutations from public apps without an allowlist are blocked.
- Nov 20, 2026 · 11:59 PM ET
Allowlist deadline for public Admin API apps; App Store delist / no new installs; flagged in Settings > Apps.
- Jan 15, 2027
Merchants see a warning in admin for apps still missing the allowlist.
- Apr 1, 2027
Admin API requests fail; existing installs kept working until this date.
A leaked Admin API token is useless if it only works from the addresses you listed.
Merchant walk-through: inventory before the 12th
If you run a store, you do not configure the allowlist yourself. The app developer does. Your job is to know which public apps talk to your Admin API, which ones already show an allowlist, and who you need to chase this week.
Open Settings > Apps. Shopify now surfaces app security setup there, including expiring tokens and IP allowlist status. After November 20, apps without an allowlist are flagged. Do not wait for the flag if bulk jobs matter to you; the bulk block lands eight days earlier.
List every public app that touches orders, inventory, catalog, fulfillment, or reporting. Those are the ones most likely to issue bulk Admin API calls. Note the vendor contact and whether the app is critical during peak week.
Ask each vendor three plain questions. Is the IP allowlist on for the production app? Did you choose static IPs/CIDR or ASN networks? Have you tested a request from outside the allowlist and confirmed a 403? If the answer to the first is no, ask for a date before November 12 for bulk-heavy apps, and before November 20 for everything else.
Decide what you will do if a vendor misses the 12th. Pause that bulk sync, switch to a manual export for a few days, or have a backup path ready. A quiet bulk job during peak week looks like missing inventory long before anyone reads a changelog.
For a sharper vendor conversation, keep the questions we wrote when Shopify last pushed app developers nearby. And if you are still sorting public App Store apps from custom installs, that distinction matters for how you commission work.
Builder walk-through: turn the allowlist on
If you maintain a public Shopify app, the Dev Dashboard path is short. Leaving it for the week of the 20th is how teams break installs during the season they cannot afford downtime.
Open Dev Dashboard → your app → Settings → Manage IP allowlist. Choose either IP addresses/CIDR ranges or Networks (ASN). Shopify does not let you mix both at once, so pick the model that matches how your servers egress.
Prefer static IPs or tight CIDR when you can. ASN support exists for serverless and other dynamic-IP setups, which is welcome. Shopify also cautions that a provider network is shared. If you must use ASN, list the countries you actually serve from, and treat the allowlist as wider than a single machine.
Run the built-in test against recent traffic (last 30 days). Shopify's docs walk this: exercise the allowlist against what you already see, then turn on Enforcement, save, and verify that a request from outside the list returns 403.
Know what the allowlist will not cover. It does not work with Shopify Flow Send HTTP request action tokens, and it does not work with GraphQL Admin API calls from an Oxygen storefront, because Shopify cannot confirm the source IP. Dev preview on development stores, and Direct API access from embedded app pages, are never rejected by this control.
Treat token hygiene as part of the same cutover. Rotating a leaked token after the allowlist is on is still useful, and rotating without a plan still breaks live traffic. Our note on rotating credentials like a cutover is the companion habit here.
Decision guide
Who does what before the deadlines
| Consideration | Merchant (Settings > Apps) | App builder (Dev Dashboard) |
|---|---|---|
| This week | Inventory public apps that touch Admin API / bulk jobs; note vendor contacts. | Open Manage IP allowlist; choose IP/CIDR or ASN (not both). |
| Before Nov 12 | Chase vendors whose apps run bulk syncs, exports, or inventory dumps. | Finish allowlist + traffic test so bulk queries/mutations keep working. |
| Before Nov 20 | Confirm allowlist status; plan for App Store flags and blocked new installs. | Turn on Enforcement, save, verify outside requests return 403. |
| After go-live | Watch Settings > Apps flags (Nov 20) and admin warnings (Jan 15, 2027). | Keep egress addresses current; revisit ASN country list if the fleet moves. |
Static IP vs ASN, and what still breaks
Two allowlist modes, one choice per app.
Static IP or CIDR. Best when your Admin API callers leave through known egress addresses: a fixed NAT gateway, a small set of app servers, a reverse proxy you control. Narrower surface, easier audits, fewer surprises when a cloud region adds capacity.
ASN / network allowlist. Built for serverless and other dynamic-IP fleets where you cannot pin a single address. Wider surface by design. Shopify's own caution applies: the provider network is shared, so prefer IPs when possible, and if you use ASN, constrain by country.
Either way, enforcement checks the source IP on GraphQL and REST Admin API calls. Outside the allowlist you get 403. You also get 403 if Shopify cannot confirm the source. That last case is why Oxygen storefront Admin API calls and Flow Send HTTP request tokens sit outside this control: the platform cannot honestly claim a source IP for them.
Plan those exceptions explicitly. If a workflow today depends on Flow firing Admin API writes with those tokens, or on storefront Oxygen code talking to Admin GraphQL, do not assume the allowlist will suddenly make that path safe. It will not. Design a different caller that sits behind addresses you can list, or keep that work on a path Shopify documents as never rejected (dev preview, embedded Direct API access) when that is actually appropriate.
Put this into practice before peak
This week, not the week of the 20th:
- Merchants: open Settings > Apps, list public apps that run bulk or Admin API work, and email vendors with a November 12 / November 20 ask.
- App maintainers: choose IP/CIDR or ASN, run the 30-day traffic test, turn Enforcement on, and confirm an outside request returns 403.
- Both sides: write down which jobs are bulk-dependent so a November 12 block does not look like a mysterious inventory outage.
- Re-check the merchant Apps screen after November 20 for flags, and again around January 15, 2027 when admin warnings land.
- Keep April 1, 2027 on the calendar as the hard Admin API failure date for apps that never finished.
If your storefront, inventory, payments, and fulfillment stack depends on public Shopify apps, our ecommerce team helps teams map that stack and keep the Admin API path honest through peak. Tell us what is on your Apps screen and we will start with the ones that move money and stock.
Related work: Paddle8.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.