Skip to content

Shopify Dude Fix

Shopify App Links Show an External-Site Warning? Declare network_access in shopify.app.toml

Shopify apps can now declare trusted navigation hosts and external request origins in shopify.app.toml. Use network_access to remove unnecessary external-site warnings and document the servers your app actually contacts.

Quick answer: If your Shopify app sends merchants or shoppers to a trusted external host, or your app code loads from or sends requests to an external server, declare those destinations in the new [network_access] section of shopify.app.toml. Use allowed_navigation_hosts for destinations people navigate to and allowed_sources for HTTPS origins your app code contacts. Deploy a new app version after adding the declarations.
On this page

Why this changed

Shopify added explicit network-access declarations on October 27, 2026. The goal is twofold: reduce friction for legitimate external navigation and give Shopify a clearer picture of the servers an app is expected to contact.

Before this change, an app could link to an external domain and Shopify could show an interstitial warning before the customer or merchant left Shopify. Developers often treated that warning as something to work around in the interface. The better fix is now configuration: declare the external hosts that are part of the intended app experience.

This also matters for requests made by app code. If an extension, app home, app proxy page, storefront script, or checkout surface talks to an API or CDN outside Shopify, that origin belongs in the app configuration.

The two network_access lists are not interchangeable

The new section has two different jobs:

  • allowed_navigation_hosts is for external hosts that a user is intentionally sent to, such as an app-owned portal, documentation site, account-management page, or another trusted destination.
  • allowed_sources is for HTTPS origins that your app code loads from or sends network requests to.

A simple configuration looks like this:

[network_access]
allowed_navigation_hosts = ["app.example.com"]
allowed_sources = ["https://api.example.com", "https://cdn.example.com"]

Notice the difference in format. Shopify’s example shows navigation hosts as hostnames and sources as HTTPS origins. Follow the current schema rather than inventing a generic list of URLs.

Build the list from real traffic, not guesses

Do not start by dumping every domain your company owns into the file. Inventory what the app actually uses.

For navigation, inspect links that leave the Shopify storefront or admin. Common examples are hosted returns portals, external account pages, financing applications, documentation, or merchant setup flows. For sources, inspect browser network requests and the code that powers extensions, app home, storefront assets, and proxies.

Pay particular attention to environment-specific hosts. A production app might use api.example.com while a development app uses api-staging.example.com. If those are separate Shopify apps, their configuration should describe the environment they actually run against rather than sharing an overbroad list.

Do not confuse network_access with an Admin API IP allowlist

[network_access] does not restrict where a stolen Admin API token can be used. It declares destinations and sources associated with the app. Shopify separately introduced an IP allowlist in the Dev Dashboard that can restrict Admin API requests to known server IPs.

These controls solve different problems. A production app may reasonably use both.

Deploying the change

After updating shopify.app.toml, deploy and release a new app version using your normal Shopify CLI flow:

shopify app deploy

Treat this like any other app configuration change. Put it in source control, review the diff, and make sure staging and production configuration do not accidentally point at each other’s infrastructure.

What to do with third-party services

If your app intentionally contacts a third-party API or CDN from a Shopify surface, declare the origin the app actually calls. Do not replace a vendor’s hostname with your own domain unless traffic genuinely goes through your domain.

Also avoid wildcard thinking. Shopify currently limits each list to 20 entries, so this is meant to describe an intentional network boundary, not act as a loose inventory of the public internet.

Common misunderstanding: “Adding network_access gives my app permission to call those servers.” It does not replace browser security rules, extension capabilities, CORS configuration, OAuth, or Shopify API scopes. It declares expected hosts and origins to Shopify. Your app still needs the normal technical permission to make the request.

How to test this

  1. Inventory every external destination and network origin used by the app in the affected Shopify surfaces.
  2. Add only the required entries to [network_access].
  3. Run shopify app deploy and release the new version.
  4. Open each external navigation path and confirm expected trusted links no longer show an unnecessary external-site warning.
  5. Exercise each app surface that calls an external API or CDN and confirm requests still succeed.
  6. Test a deliberately undeclared or incorrect host in a development environment so you understand the failure or warning behavior before production.
  7. Review the list again after removing an integration. Network declarations should shrink when the app stops using a host.