Shopify merchants and developers have long juggled two separate interfaces for managing apps: the storefront admin for custom integrations and the Dev Dashboard for public and private apps. As of the latest Developer Changelog, that split is ending. Custom apps that were originally created directly in the Shopify admin now appear side‑by‑side with every other app in the Dev Dashboard. This shift brings a single pane of glass for credentials, IP restrictions, and activity logs, without breaking any existing integrations.
What Changed? Admin‑Created Custom Apps Move to the Dev Dashboard
Previously, a merchant could spin up a custom app from Settings → Apps and manage its API key and secret in the admin UI only. Those apps were invisible in the Dev Dashboard, meaning developers couldn’t see logs or set IP allowlists without digging into the admin. The update migrates every custom app created in the admin into the Dev Dashboard automatically. The migration preserves the app’s installed status, access scopes, webhook subscriptions, and any existing Admin API access tokens. No code changes are required for the app to keep working.
Who Is Affected?
The change impacts three groups: (1) merchants who have built a custom app directly in their store’s admin, (2) staff members who created a custom integration on behalf of a merchant, and (3) developers who receive a transferred custom app from a client. Public apps, private apps that were already managed in the Dev Dashboard, and any app types that never lived in the admin remain untouched. In short, if the app’s origin is the admin UI, it will now surface in the Dev Dashboard.
Why It Matters: Security and Visibility
Centralizing app management reduces friction and opens new security controls. The Dev Dashboard now lets you:
• Configure IP restrictions (allowlists) that limit which server IPs can use the app’s credentials, mitigating credential leakage.
• Inspect detailed API request logs and webhook delivery logs, making it easier to audit traffic, spot anomalies, and debug integration issues.
• View and rotate API keys or secret tokens from the same interface you already use for public and private apps.
These capabilities were previously scattered across the admin settings, the Shopify Partners portal, and third‑party monitoring tools. Bringing them together improves operational efficiency and reduces the attack surface for custom integrations.
How to Verify the Migration
After the rollout, log in to your Partner or Shopify Plus organization and navigate to the Dev Dashboard (partners.shopify.com > Apps). You should see a new entry for each custom app that originated in the admin, listed with its name, installation status, and granted scopes. Click the app to view the Credentials tab – the API key and secret will be displayed, and a note will indicate that the app was migrated from the admin. If anything looks missing, double‑check that you’re looking at the correct merchant account, as the migration only applies to that store’s admin‑created apps.
Enabling IP Restrictions
IP allowlisting is optional but highly recommended for production environments. From the app’s Details page in the Dev Dashboard, select “IP Restrictions” and add the IPv4 or IPv6 ranges that are allowed to call the API. The UI stores the ranges, and Shopify automatically rejects any request that originates from an unapproved IP.
# Example GraphQL mutation to set allowed IPs via the API (if you prefer automation)
mutation updateAppIPAllowlist($appId: ID!, $ips: [String!]!) {
appUpdate(input: {id: $appId, ipAllowlist: $ips}) {
app {
id
ipAllowlist
}
userErrors {field message}
}
}
Replace $appId with the app’s GraphQL ID (e.g., "gid://shopify/App/123456789") and $ips with an array of strings such as ["203.0.113.10/32", "198.51.100.0/24"]. After the mutation succeeds, test the integration from an allowed IP and watch the Dev Dashboard logs for successful calls.
Using Logs for Troubleshooting
The Dev Dashboard now aggregates both API request logs and webhook delivery logs for migrated custom apps. Filter by date, endpoint, response status, or webhook topic to pinpoint failures. For example, if a recent webhook stopped firing, you can open the webhook logs, see the HTTP response code, and identify whether the issue is a 401 (invalid token), a 403 (IP restriction), or a 500 (internal server error). This visibility shortens the mean‑time‑to‑resolution from hours to minutes.
Next‑Step Checklist
✅ Log into the Dev Dashboard and confirm each admin‑created custom app appears with the correct scopes.
✅ Review the Credentials tab and record the current API key/secret for your documentation.
✅ Enable IP restrictions where you control the originating servers; add known IP ranges.
✅ Use the API and webhook logs to verify that requests after enabling IP allowlist succeed.
✅ Set up a monitoring window (24‑48 hours) to watch for unexpected 401/403 responses.
✅ Document the new location of the app in your internal runbooks so future team members know to use the Dev Dashboard for any changes.
Conclusion & Call to Action
Migrating admin‑created custom apps into the Dev Dashboard is a quiet but powerful upgrade that gives you centralized security controls and full visibility into integration traffic. While no immediate action is required to keep your apps running, taking a few minutes now to review each app, enable IP allowlists, and familiarize yourself with the new logs will pay dividends in security and support efficiency. Need help configuring IP restrictions or interpreting logs? Reach out to your Shopify Partner or drop a comment below—we’re happy to walk you through the process.
