403 immediately after you enable Shopify’s new IP allowlist, first verify the public egress IP address of every server, worker, queue consumer, and scheduled job that uses the app’s access tokens. A valid token from an address outside the configured ranges is supposed to fail.On this page
What the IP allowlist actually protects
Shopify introduced an Admin API IP allowlist on October 27, 2026. When enabled, Shopify accepts Admin API requests made with your app’s tokens only from the public IP addresses or CIDR ranges you configured in the Dev Dashboard.
This adds a second boundary around a credential. A leaked access token might still be valid, but it cannot be used from an arbitrary machine if the request originates outside your approved network.
Shopify’s own security guidance describes the relationship clearly: expiring access tokens limit how long a leaked credential works; an IP allowlist limits where it can work.
Why a correct app can suddenly get 403 responses
The common failure is not OAuth. It is infrastructure.
Your backend may look like one application in a diagram while outbound requests actually leave through several addresses. Examples include:
- a web server and a separate background worker;
- scheduled jobs running on a different host;
- a queue service with its own egress;
- blue/green production environments;
- multiple regions;
- a failover server;
- a NAT gateway that changed;
- a serverless host that does not guarantee static egress.
If any of those processes call the Admin API using the protected app’s tokens, their egress addresses need to be represented before you turn enforcement on.
Do not rotate a healthy token to fix an IP failure
A 403 after allowlist enforcement can look like an authentication problem. Resist the instinct to regenerate credentials immediately.
First compare timing. Did the failures begin when the allowlist was enabled? Are requests from one service succeeding while another service fails? Does the same token succeed from an allowed production host?
If yes, investigate source IP before touching scopes, reinstalling the app, or forcing merchants through OAuth again.
Use Shopify’s traffic test before enforcement
The Dev Dashboard lets you enter addresses or CIDR ranges and test them against recent app traffic before enabling the restriction. Use that step as a deployment gate.
The goal is to identify legitimate recent traffic that falls outside the proposed ranges. If the test shows unknown addresses, trace them back to your infrastructure instead of blindly adding them. An allowlist that contains every address you cannot explain defeats much of the point.
Serverless needs special attention
Shopify’s October 27 changelog notes that support for serverless platforms with dynamic IP addresses is coming soon. That matters because many modern app backends do not leave through a fixed public IP by default.
If your host uses dynamic egress, do not enable a static allowlist until you have a supported fixed-egress design or Shopify’s serverless support applies to your deployment. Otherwise normal production traffic can be blocked.
Operationalize the setting
Once enabled, document the allowed addresses next to your infrastructure configuration. If an operations team changes a NAT gateway or moves a workload, the Shopify allowlist becomes part of the change plan.
Also monitor 403 responses from your own servers. Shopify recommends treating unexpected 403s from an approved environment as a signal that you forgot an address or your network path changed.
One current limitation is worth noting: the IP allowlist lives in the Dev Dashboard. The separate [network_access] section in shopify.app.toml does not configure this credential-level allowlist.
shopify.app.toml, my Admin API token is restricted to that server.” No. [network_access] describes hosts and origins used by app code. The Admin API IP allowlist is a separate Dev Dashboard security control based on the public source IP of requests using your tokens.How to test this
- List every workload that makes GraphQL or REST Admin API requests for the app.
- Record the public egress IP or CIDR range for each workload.
- Enter the proposed ranges in the Dev Dashboard and run Shopify’s recent-traffic test before enforcement.
- Enable the allowlist in a controlled window.
- Run a harmless Admin API query from every legitimate workload and confirm success.
- Make the same request with a test token from a machine outside the allowlist and confirm Shopify returns
403. - Confirm your monitoring alerts on unexpected 403 responses from production.
- Document the allowlist as a dependency of future infrastructure migrations.
Sources and further reading
- Shopify developer changelog: Restrict Admin API access with an IP allowlist
- Shopify developer documentation: Restrict API access to your IP addresses
- Shopify developer blog: Security update — October 2026
Documentation reviewed October 28, 2026.

