App security updates: IP allowlist now required for public apps
Public apps that call the Admin API must turn on an IP allowlist by 20 November 2026, or 12 November 2026 for bulk operations, or face delisting and blocked requests.

- Published
- 17 Nov 2026
- Affects
- Admin API, Bulk operations
What changed
On 27 October 2026 Shopify recommended that apps use an IP allowlist. In a changelog post dated 5 November 2026, it made the allowlist a requirement for every public app that calls the Admin API.
With the allowlist on, your app's tokens only work from the addresses or networks you list. A leaked token then cannot be used from anywhere else. Shopify says it is asking for this now because the busiest weeks of the year for merchants are almost here.
If your app runs on serverless hosting or uses dynamic IPs, you cannot list fixed addresses. Shopify says to allowlist by network instead, using its ASN support.
Who is affected
The IP allowlist requirement applies to every public app that calls the Admin API. Public apps that run bulk queries or mutations are also affected, and they have an earlier date for those operations (see the deadlines section).
The changelog does not mention custom apps in connection with the IP allowlist. It does not say whether the requirement applies to them, so check with Shopify before assuming either way.
The expiring offline access token timeline is unchanged. It applies to public apps that still use non-expiring offline access tokens for the GraphQL Admin API or REST Admin API. The migration page says none of that timeline applies to custom apps, apps created by merchants, or Payments Apps API requests.
Merchants are affected indirectly. Shopify says they can now see an app's security setup in Settings > Apps, and apps without an IP allowlist will be flagged there after 20 November 2026.
What to do
Work through these steps in order. The first two cover the allowlist itself, which is the new requirement. The rest are related checks from the same announcement.
Turn on the IP allowlist
If your public app calls the Admin API, turn on the IP allowlist and list the addresses or networks your servers use. Your tokens will then work only from those places.
If you host on serverless or dynamic IPs, allowlist by network using ASN support instead of listing individual addresses. Shopify has a separate changelog post on ASN support for serverless hosting: https://shopify.dev/changelog/posts/app-ip-allowlists-now-support-apps-with-serverless-hosting
If your app runs bulk queries or mutations, do this first, because bulk operations have an earlier cut-off than other Admin API calls.
Check for non-expiring tokens
The expiring offline token timeline is unchanged, but the announcement asks you to check for non-expiring tokens at the same time. In the Dev Dashboard, open your app's Logs and filter Type to GraphQL request, then filter Token type to Offline, non-expiring. If your app also makes REST Admin API requests, repeat the check with Type set to REST request.
Migrate to expiring offline tokens
If your app is built from an app template (@shopify/shopify-app-remix or @shopify/shopify-app-react-router), set the expiringOfflineAccessTokens flag in shopifyApp() and redeploy with shopify app deploy.
If you implement token exchange or the authorization code grant yourself, add expiring=1 to the token request, and store the access token, refresh token and both expiry values.
To move existing installs without waiting for users to open your app, use the direct migration flow on the migration page. It permanently invalidates the old token for Admin API requests, so store the new access and refresh tokens from the response.
Optional checks
Test your network_access declarations before release. Run shopify app dev --store <your-dev-store>.myshopify.com on a dev store with the Network access testing feature preview. Shopify describes this preview as under development, so its behaviour might change.
Run app security checks in CI/CD. Shopify's tutorial describes a pipeline that runs shopify app security check --skip-instructions and then shopify app security review --blocking high, and gives a GitHub Actions and Codex example.
shopify app security check --skip-instructions
shopify app security review --blocking highDeadlines and consequences
These dates come from the "If you miss a deadline" table in the changelog, dated 5 November 2026. The changelog says that existing installs keep working until 1 April 2027 for both the IP allowlist and expiring offline access tokens.
The IP allowlist for all other Admin API calls from public apps must be on by 20 November 2026 at 11:59 PM ET. The table below sets out what happens at each date.
Consequences by date (IP allowlist | expiring offline access tokens):
Bulk queries and mutations blocked: 12 November 2026 for the IP allowlist; no date given for expiring tokens.
Delisted from the App Store, no new installs: 20 November 2026 for the IP allowlist; 1 January 2027 for expiring tokens.
Flagged in merchant Settings > Apps: 20 November 2026 for the IP allowlist; 1 January 2027 for expiring tokens.
Merchants see a warning in their admin: 15 January 2027 for both.
Admin API requests fail: 1 April 2027 for both.
For expiring tokens, the migration page adds that from 1 April 2027 Shopify rejects Admin API requests that present a non-expiring offline token, and merchants lose access to your app until they re-authenticate.
Before and after: token migration
These snippets come from the migration page. They cover the token exchange request and the app template flag. The IP allowlist itself needs no code change in these sources.
Token exchange request
Add expiring=1 to your existing ID-token exchange request. The authorization code grant request takes the same parameter. Store the access_token and refresh_token from the response, along with expires_in and refresh_token_expires_in.
Before
curl -X POST \
https://{shop}.myshopify.com/admin/oauth/access_token \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'grant_type=urn:ietf:params:oauth:grant-type:token-exchange' \
-d 'subject_token={id_token}' \
-d 'subject_token_type=urn:ietf:params:oauth:token-type:id_token' \
-d 'client_id={client_id}' \
-d 'client_secret={client_secret}'After
curl -X POST \
https://{shop}.myshopify.com/admin/oauth/access_token \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'grant_type=urn:ietf:params:oauth:grant-type:token-exchange' \
-d 'subject_token={id_token}' \
-d 'subject_token_type=urn:ietf:params:oauth:token-type:id_token' \
-d 'client_id={client_id}' \
-d 'client_secret={client_secret}' \
-d 'expiring=1'App template flag
If your app uses @shopify/shopify-app-remix or @shopify/shopify-app-react-router, add the flag to your shopifyApp() configuration and redeploy with shopify app deploy. The template then stores and refreshes expiring tokens itself.
Before
const shopify = shopifyApp({
// ...
});After
const shopify = shopifyApp({
// ...
future: {
expiringOfflineAccessTokens: true,
},
});Also announced and still unknown
The same changelog post lists several other changes. None of them has its own deadline, apart from the flagging date covered in the deadlines section.
Security setup visible to merchants
Merchants can now see your app's security setup in Settings > Apps. This covers expiring tokens and the IP allowlist. After 20 November 2026, apps without an IP allowlist are flagged there.
Network access testing in dev store previews
You can test your network_access declarations before you release. The test flags any site or server your app uses that you have not declared. It needs a dev store with the Network access testing feature preview, and you run your app on that store with shopify app dev. On that store, links to undeclared hosts show the exit prompt, and the browser console warns when a page connects to an undeclared server.
Security checks in CI/CD
A new tutorial shows how to scan your app for security issues automatically on every change. Its pipeline runs shopify app security check --skip-instructions and shopify app security review --blocking high, then an optional coding agent review, and makes the final decision a required check before merging. It includes a worked example for GitHub Actions and Codex. The agent review sends your source code to its model provider.
Still unknown: bulk operation access scopes
Shopify says bulk queries and bulk mutations will each need their own access scope, and that this is coming soon. The scope names and the release date have not been announced. Shopify says it will publish a changelog with the scope names when they are ready.
If your app ran a bulk operation in the last 180 days, Shopify grants the scopes automatically. Once they are live, add them to your app configuration before your next deploy. Until the names are published, there is nothing to add.
Get the weekly digest
One email every Monday: what changed in Shopify, the deadlines coming up and what’s been announced, plus the week’s new guides. Free, and you can unsubscribe in one click.
Sources
- App security updates: IP allowlist is now required · Shopify · accessed 5 Nov 2026
- Migrate to expiring offline access tokens · Shopify · accessed 5 Nov 2026
- Declare your app's network access · Shopify · accessed 5 Nov 2026
- Run app security checks in CI/CD · Shopify · accessed 5 Nov 2026
AI-assisted, reviewed by Scott. Every claim is checked against the sources above.