Guide
Shopify IP allowlist required: what to do before 20 November (custom and public apps)
How this guide was made: Written with AI assistance and checked against the sources linked on this page.
Updated
Short answer: Shopify's new installs are blocked for apps without an IP allowlist from 20 November 2026, 11:59 PM ET (custom apps installed outside your organization, and public apps). Custom apps already installed on stores outside your organization need one by 1 January 2027, 11:59 PM ET. The one action: open your app in the Dev Dashboard, add your server's outgoing IP addresses (or your host's ASNs), run the test, and turn on Enforcement.
Key takeaways
- Custom apps installed on stores outside your own organization need an allowlist for new installs from 20 Nov 2026 (11:59 PM ET) and for existing installs from 1 Jan 2027 (11:59 PM ET).
- Public apps without an allowlist are delisted from the Shopify App Store and blocked from new installs on 20 Nov 2026. Public apps that use bulk operations had an earlier date, 12 Nov 2026.
- Requests from outside the list fail with a 403 on the GraphQL and REST Admin APIs.
- If your host has no fixed outgoing IP, Shopify lets you allow your host's ASNs (up to 10) and limit them to the countries your app runs in. IP addresses are the narrower option.
- Apps used only inside your own organization, and apps merchants create themselves, are not required to have one.
Who is affected by the Shopify IP allowlist requirement?
Custom apps: an allowlist is required for apps installed on stores outside the organization that owns the app. Shopify's docs say: "We also highly recommend IP allowlists for apps installed only on stores in your own organization, though they aren't required." Shopify's changelog says apps created by merchants in the Dev Dashboard or in the admin are not affected.
Public apps: all public apps are covered by a separate requirement with its own dates (below).
Some traffic does not work with an allowlist: access tokens used by the Shopify Flow "Send HTTP request" action are rejected, and so are tokens used for GraphQL Admin API requests from an Oxygen-hosted storefront. Dev preview requests on dev stores, direct API access from your app's embedded pages, and direct API access from POS UI extensions are never rejected.
What breaks, and when?
Custom apps installed outside your organization (all times ET, per Shopify's IP allowlist docs at shopify.dev/docs/apps/build/dev-dashboard/ip-allowlist; Shopify's 5 November changelog covers public apps only):
- 20 November 2026, 11:59 PM: the app must have an allowlist to be installed on new stores.
- 1 January 2027, 11:59 PM: allowlists are required for existing installs too.
Public apps:
- 12 November 2026, 11:59 PM ET: bulk queries and bulk mutations from public apps without an allowlist are blocked.
- 20 November 2026, 11:59 PM ET: public apps without an allowlist are delisted from the Shopify App Store and blocked from new installs. Merchants see a flag in Settings > Apps. Existing installs keep working.
- 15 January 2027: merchants using the app see a warning in the Shopify admin.
- 1 April 2027: Shopify rejects the app's GraphQL and REST Admin API requests.
What a blocked call looks like: when enforcement is on, Admin API requests that use your app's tokens from outside the allowlist fail with a 403 status code. So do requests whose source address Shopify cannot confirm. If your app breaks right after you turn Enforcement on, a 403 from the Admin API is the first thing to look for in your logs.
How do I add the IP allowlist in the Dev Dashboard?
These are Shopify's steps:
- In the Dev Dashboard (dev.shopify.com/dashboard), open your app, click Settings, then click Manage in the IP allowlist section.
- Enter IP addresses or CIDR ranges, ASNs, and (under "Limit ASNs to countries") the countries your app runs in.
- Under "Test against recent traffic", click Run test. It checks your addresses from the last 30 days. If any would be blocked, adjust the list and test again. Results can take a few minutes to include the latest requests.
- Turn on Enforcement, then click Save.
- Make a GraphQL Admin API request from outside your allowlist and confirm it returns a 403.
To stop enforcement, turn Enforcement off and click Save. Shopify keeps your allowlist so you can re-enable it later.
Limits from Shopify's page:
- Up to 250 IP addresses or ranges, one per line, in CIDR notation (for example 203.0.113.0/24).
- Use /16 or narrower for IPv4 and /32 or narrower for IPv6. Start each range at its network address (203.0.113.0/24, not 203.0.113.7/24).
- Public addresses only. If your servers sit behind a NAT gateway, allow the gateway's addresses.
- IPv6 is accepted. Include IPv6 addresses if your servers reach Shopify over IPv6.
- Up to 10 ASNs (public only) and up to 10 countries. Countries narrow only ASNs, not IP addresses, and you cannot pick countries without ASNs. Without countries, an ASN is allowed from anywhere.
- If a list has both, Shopify checks IP addresses first.
How do I find my app's outgoing IP?
Two ways that Shopify documents:
- Open your app's Logs in the Dev Dashboard and check the client IP addresses on recent Admin API requests. Shopify's page points here for finding your host's ASN as well.
- Use "Run test" in the allowlist screen. It checks your addresses from the last 30 days and tells you if any would be blocked.
Your host's own docs also list its outgoing addresses or ranges, if it has any (see the table below). Test against recent traffic before you turn Enforcement on.
Which hosts give a fixed outgoing IP?
Read on 15 November 2026 from each host's own pages. Prices are quoted only as the host's page states them; "not stated" means the page I read gave no price.
| Host | Fixed outgoing IP? | How | Price as the host states | Page read |
|---|---|---|---|---|
| Heroku | Yes, two routes | Private Spaces: outbound traffic comes from "a small, stable list of IP addresses dedicated to the space". Or add-ons listed on Heroku Elements, such as Fixie and QuotaGuard Static, which proxy requests through fixed IPs | Private Spaces: not stated on the page (available for verified Heroku Teams and Heroku Enterprise). Fixie listing: plans from free up to "Max of $1999/month". QuotaGuard Static listing: Starter free, up to "Max of $1599/month" (Unlimited) | devcenter.heroku.com/articles/private-spaces; devcenter.heroku.com/articles/fixie; elements.heroku.com/addons/fixie and /quotaguardstatic |
| Render | Yes | Dedicated IPs: each set includes three IPv4 addresses | Docs say "an additional monthly fee for each IP set"; amount not stated on the docs page. Requires a Pro workspace plan or higher. Default outbound ranges are shared, not static | render.com/docs/dedicated-ips; render.com/docs/outbound-ip-addresses |
| Vercel | Yes | Static IPs (shared pool): two static IPs per configured region, up to three regions; for functions, and for builds if you turn on "Use for builds". Not used by Routing Middleware | "$100/month per project for Pro" plus Private Data Transfer at regional rates. Available on Pro and Enterprise | vercel.com/docs/networking/static-ips (page lists last_updated 2026-06-30) |
| Railway | Yes | Static Outbound IPs per service; redeploy after enabling. Highly available services get three IPs; Railway says they may be shared | Pro plan; price not stated on the page | docs.railway.com/networking/static-outbound-ips |
| Netlify | Yes, on Enterprise only | Private Connectivity for functions (regions cmh, fra, lhr); not available for Edge Functions | Add-on to Enterprise plans; price not stated, contact Netlify | docs.netlify.com/manage/security/private-connectivity/ |
| Supabase Edge Functions | No | Supabase says Edge Functions "do not originate from a single static IP address or a small, stable range of IPs" | Not applicable | supabase.com/docs/guides/troubleshooting/why-supabase-edge-functions-cannot-provide-static-egress-ips-for-whitelisting-3d78b0 |
| Cloudflare Workers | No documented fixed IP for Workers | Cloudflare's dedicated egress IPs are a Zero Trust feature; its page does not mention Workers | Add-on to Zero Trust Enterprise plans; price not stated | developers.cloudflare.com/cloudflare-one/traffic-controls/egress-policies/dedicated-egress-ips/ |
Notes: Heroku's Fixie and QuotaGuard are third-party add-ons sold through Heroku Elements; check the current plan list on those pages before buying. I did not find a Netlify, Supabase or Cloudflare Workers page stating a fixed outgoing IP on a self-serve plan.
What if my host has no fixed outgoing IP?
Shopify and the hosts document these options:
- Allow your host's ASNs instead of addresses. Shopify's page says to do this for dynamic IPs, "as on most serverless platforms", and to list only the countries your app runs in. You can enter up to 10 ASNs. Shopify notes a provider's network is shared with its other customers, so addresses are the narrower option when you can use them.
- Run the Shopify API calls from a host or service that has a fixed outgoing IP (for example, one of the options in the table), and have your app call that service.
- Send the calls through a proxy with a fixed IP. Supabase's own guide recommends this for Edge Functions: route requests through a proxy server with a fixed IP and allow that IP. On Heroku, the Fixie and QuotaGuard add-ons work this way.
- Supabase's guide also describes running the open-source Edge Runtime on a server with a static IP you control.
Whichever you pick, run "Test against recent traffic" in the Dev Dashboard before turning Enforcement on.
FAQ
Is an allowlist required for an app used only on my own store?
Shopify's docs say an allowlist is highly recommended, but not required, for apps installed only on stores in your own organization. Its changelog says apps created by merchants in the Dev Dashboard or the admin are not affected.
What error will my app see if the IP is not on the list?
Shopify's page says requests from outside the allowlist fail with a 403 status code, and so do requests whose source address Shopify cannot confirm. This applies to GraphQL Admin API and REST Admin API requests that use your app's tokens.
Can I use IPv6 or a range of addresses?
Yes. Shopify accepts CIDR ranges (/16 or narrower for IPv4, /32 or narrower for IPv6), up to 250 entries, and says to include IPv6 addresses if your servers reach Shopify over IPv6.
My app runs on serverless functions with changing IPs. What now?
Use ASNs. Shopify says dynamic IPs are common on serverless platforms and to allow your hosting provider's ASNs (up to 10) plus the countries your app runs in. If the data has no ASN for an address, the request is rejected, so test against recent traffic first.
Can VibeFix fix it for me?
Yes, for apps built in Lovable or any app whose code is on GitHub. The free check confirms the problem on your live app first. If you want it fixed, our AI agent finds the cause, fixes it in your code for $79 and tests your live app again. See pricing.
Sources
- Shopify: Restrict API access with an IP allowlist
- Shopify changelog: IP allowlists are now required for public apps
- Shopify changelog: App IP allowlists now support apps with serverless hosting
- Supabase: Why Edge Functions cannot provide static egress IPs
- Vercel: Static IPs
- Render: Dedicated IPs
- Railway: Static outbound IPs
VibeFix is independent. Shopify is a trademark of Shopify Inc.
Want it fixed?
Our AI agent fixes it in your code for $79 and tests your live app again. If we can't complete your re-check, you get your money back.
It starts with a free check that confirms the problem on your live app, no account needed.
More guides · Shopify store accessibility · About · Your privacy choices