Description

Shopify is introducing mandatory IP allowlisting for public applications that access its Admin API, strengthening security against unauthorized access and stolen authentication tokens. Developers must enable this security measure by November 20, 2026, at 11:59 PM ET. However, applications that use bulk operations must meet an earlier deadline of November 12, 2026. The policy builds on a security feature Shopify introduced on October 27, 2026. Under the new requirement, Shopify will verify the origin of API requests instead of depending entirely on valid access tokens. This additional layer helps prevent attackers from accessing merchant information and services using compromised credentials. Once IP allowlisting is enabled, Shopify checks incoming GraphQL Admin API and REST Admin API requests against the approved IP addresses or networks configured by developers. Requests originating outside the permitted network will receive an HTTP 403 Forbidden response. Requests with an unverified source address may also be rejected. Developers who fail to meet the November 20 deadline risk having their applications removed from the Shopify App Store, with new installations blocked. Existing installations can continue working until April 1, 2027, after which their Admin API requests will stop functioning. Bulk queries and mutations have the earlier November 12 deadline. Shopify will also begin sending administrative warnings to merchants on January 15, 2027. To implement this requirement, developers can configure approved IP addresses or network ranges through the Settings section of the Shopify Dev Dashboard. Applications operating with dynamic IP addresses can use Autonomous System Numbers (ASNs), with support for up to 10 ASNs and restrictions covering up to 10 countries. Shopify recommends reviewing recent API traffic before enforcing the restriction to avoid interrupting legitimate operations. Developers should also test requests from unapproved networks to confirm that access is properly blocked. Together, IP restrictions and expiring tokens provide stronger protection, although developers must continue following good credential management practices to reduce security risks.