ProductHow it worksDocsBlogPricingSign inGet Framer Plugin
← Blog

Shopify Developer Portal: What Framer Designers Actually Need

To connect a Framer site to Shopify you need exactly three things from the Shopify developer portal: a storefront with Storefront API access, the minimum read scopes for products and cart, and the public storefront access token. You do not need a Partner account, an app listing, or any code review. What changed in 2026 is where you get them, and most tutorials still send you to a screen that no longer works.

That gap is the whole problem. Every official doc for this is written for someone shipping an app to thousands of merchants, so the designer who just wants product data on a Framer page reads four pages about OAuth and gives up.

What Is the Shopify Developer Portal, and Which Part Do You Need?

The "Shopify developer portal" is not one product. In practice people mean one of three surfaces, and only two of them still issue the token a Framer site needs.

The Dev Dashboard on shopify.dev is where custom apps now live. The Headless sales channel, installed into your own store from the Shopify App Store, is a self-serve generator for Storefront API tokens. The third surface is the old Apps › Develop apps screen inside your Shopify admin, which is where almost every tutorial published before this year points you.

Define it narrowly and the job gets small: you are creating a credential that lets a public web page read your catalog. Nothing more.

The Route That Closed on January 1, 2026

Shopify shut the admin-created custom app path to new builds this year. If you follow an older walkthrough, you will find the button missing and assume you lack a permission.

You can no longer create new admin-created custom apps. Existing apps are unaffected and continue to work. — Shopify developer documentation

Existing credentials keep working indefinitely, and legacy custom apps created before January 1, 2026 are still managed from the Shopify admin. Everything new goes through the Dev Dashboard or the Headless channel. This also quietly changed who can do the setup at all: the Dev Dashboard needs the App developer role on the organization, and collaborator accounts cannot access the Dev Dashboard because they have no organization-level permissions. Agencies working on a client store under a collaborator invite hit a wall here that has nothing to do with scopes.

Where Do You Get a Shopify Storefront API Token Now?

The Headless channel is the shortest path, and it is the one to use unless you are genuinely building an app. Install it into the store, create a storefront, and it hands you a public and a private token with Storefront API permissions already attached. You can run a maximum of 100 active storefronts and access tokens per shop, which is far more than any agency needs.

Two tokens come out, and mixing them up is the most common security mistake in this workflow. The public token goes in the X-Shopify-Storefront-Access-Token header and is designed to be visible in the browser. The private token uses Shopify-Storefront-Private-Token, and Shopify is blunt that private access tokens should be treated as secret and not used on the client-side. A Framer site is a client. Use the public one.

There is also a tokenless tier that covers products, collections and cart with a query complexity limit of 1,000 — enough to prototype a product grid before you touch credentials at all.

Which Scopes Does a Framer Storefront Actually Need?

Four read scopes cover a working storefront. Everything else on the list is for features you probably are not shipping in week one. Here is the whole setup, step by step, with what actually breaks if you skip each one.

Step Where in Shopify Token or scope involved What breaks if you skip it Does a Framer plugin do it?
1. Create the storefront Headless channel → Create storefront Public + private access token issued No credential at all; every query returns 401 No — one-time store setup
2. Allow catalog reads Headless channel → Storefront API permissions unauthenticated_read_product_listings Products and collections return null No
3. Allow stock reads Same permissions screen unauthenticated_read_product_inventory No quantityAvailable; sold-out items stay buyable No
4. Allow cart writes Same permissions screen unauthenticated_write_checkouts Add-to-cart fails silently; no checkout URL No
5. Allow variant plans (subscriptions only) Same permissions screen unauthenticated_read_selling_plans Subscription options vanish from variants No
6. Pin the API version Your request URL /api/2026-10/graphql.json Shopify falls forward to the oldest stable version Yes — the plugin manages the version
7. Paste the public token Framer plugin settings X-Shopify-Storefront-Access-Token Nothing renders Yes — this is the only step a plugin owns

Scope names are exact and case-sensitive; the full list of unauthenticated Storefront access scopes also covers product tags, metaobjects, pickup locations and blog content, and any write scope grants read on the same resource. Steps 1 through 5 happen once per store, by hand. A plugin like FramerLink picks up at step 6, so the work in the developer portal is a ten-minute job you never repeat — the ongoing part is keeping products in sync, not managing credentials.

Do You Need a Shopify Partner Account to Connect Framer?

No. A Partner account exists to list apps in the Shopify App Store, bill merchants, and manage development stores for clients. None of that is involved in reading your own catalog. The one case where a Partner account helps is agency work: free development stores to build against before a client's real store goes live. For a single storefront, skip it.

What Breaks When Your API Version Goes Stale

Version drift is the failure mode that hits months after launch, when nobody is looking. Shopify releases a new API version every three months and supports each stable version for a minimum of 12 months, with at least nine months of overlap between consecutive versions. As of this month, 2026-10 is the latest stable release and the 2025 versions are already unsupported.

Miss the window and requests do not fail loudly. Shopify falls forward to the oldest accessible stable version, so a field you depended on quietly returns something else. The same clock is running on customer accounts: legacy customer accounts became unavailable to new stores in February 2026, Storefront API customer mutations are slated for deprecation, and the Customer Account API is now the only supported source for authenticated buyer actions. If your Framer build has a login, that is the piece to check before anything else.

Put a calendar reminder on the quarter. Audit your pinned version once, confirm your scopes still match the features you shipped, and the developer portal stops being something you think about. Our guide to the 2026-07 Storefront API changes walks through what moved last cycle, and if the whole token-and-scope model still feels abstract, headless architecture explained for designers covers why this separation exists at all. The pairing walkthrough has the exact screens.

Frequently asked questions

What is API on Shopify?

A Shopify API is an endpoint your site queries for store data. The Storefront API returns products, collections and cart data for public storefronts. The Admin API manages the store itself, and the Customer Account API handles logged-in buyers. A Framer storefront uses the Storefront API only.

Is the Shopify API free?

Yes. Shopify does not charge for API access on any paid plan, and creating apps or storefronts in the Dev Dashboard costs nothing. You pay for your Shopify subscription and for whatever hosts your frontend. Rate limits, not fees, are the practical ceiling on Storefront API usage.

Is there a REST API for Shopify?

Shopify's Admin API still exposes REST endpoints, but GraphQL is now the documented path for new builds and the Storefront API is GraphQL-only. A Framer storefront sends POST requests to a single GraphQL endpoint, so there is no REST route to set up for product or cart data.

Sources