Shopify API Basics for Framer Designers: Admin vs Storefront
The Shopify API is not one API. The Storefront API serves public catalog and cart data to a customer-facing site like a Framer storefront. The Admin API manages products, inventory and orders behind the scenes, and it must never be exposed in a browser. Everything else — customer logins, checkout configuration, webhooks — sits around those two.
That distinction is the whole thing. Almost every security incident and every "why is this so slow" complaint in a headless build traces back to someone using the wrong one of those two. You do not need to write GraphQL to design a good Shopify store in Framer. You do need to know which API owns which job, which one is safe in the browser, and which one quietly expires.
Which Shopify APIs are there, and what does each one do?
There are five surfaces worth knowing. Two you will touch constantly, one you will touch the moment you add logins, and two you should recognize when a developer mentions them.
| API | What it's for | Framer store touches it | Security rule | Versioned |
|---|---|---|---|---|
| Storefront API | Public products, collections, cart | Yes, via plugin or integration | Public token, safe in the browser | Yes, quarterly |
| Admin API | Products, inventory, orders, back office | No, server-side only | Secret token, never client-side | Yes, quarterly |
| Customer Account API | Buyer login, order history, addresses | Only when you add accounts | OAuth 2.0 with PKCE | Yes, quarterly |
| Checkout & Accounts Configuration | Branding and behavior of hosted checkout | Rarely, usually once at setup | Admin-level credentials | Yes, quarterly |
| Webhooks | Push notifications when store data changes | Indirectly, through your sync tool | Verify every payload signature | Yes, same cadence |
The pattern is consistent: anything a shopper is allowed to see is public and cheap to call, and anything a merchant controls is private and rate-limited.
Storefront API vs Admin API: which one does a Framer site use?
A Framer storefront reads from the Storefront API, directly or through whatever plugin handles the connection. It never talks to the Admin API from the browser.
The numbers explain why. The Admin API is metered hard: Shopify allows 100 cost points per second on standard plans and 1,000 on Plus, with a single query capped at 1,000 points regardless of tier. The legacy REST Admin API is tighter still, at two requests per second on a standard plan. Those budgets are built for background jobs, not for a product page being loaded by a thousand shoppers at once.
The Storefront API is the opposite. Shopify applies no fixed request-per-minute limit to buyer traffic on the Storefront API — it is designed to absorb a flash sale. That is the entire reason it exists as a separate surface.
The security rule follows the same line. A Storefront access token is designed to be public and exposes a deliberately narrow slice of data. An Admin token can read customer PII and move money, so it lives on a server and nowhere else. If anyone suggests putting an Admin token into a Framer page, a code component, or a custom embed, that is the end of the conversation. For how the catalog side of this actually gets wired up, see our walkthrough of syncing products into Framer pages.
What Shopify API pricing actually covers
There is no line item called "API" on a Shopify invoice. Access comes with the plan, which is why the honest answer to the pricing question is that your API cost is your subscription cost.
What your plan does buy is throughput. Moving up a tier raises the points-per-second ceiling on the Admin API and the Customer Account API; it does not unlock endpoints that lower tiers cannot see. So if you are on Basic and a sync feels sluggish, the fix is usually a smarter query, not a bigger plan. Third-party tools in the middle — sync apps, plugins, headless services — carry their own pricing, and that is where real costs show up.
REST or GraphQL: which Shopify API style should you plan around?
GraphQL, in every case where you have a choice.
Shopify has consolidated on GraphQL as the primary interface. The REST Admin API still works and still returns data, but it is a legacy surface: new fields and capabilities are added to the GraphQL Admin API, and the Storefront API and Customer Account API are GraphQL-only by design. If you are scoping a build in 2026 and someone proposes REST because it is familiar, you are buying a migration.
For designers, the practical consequence is small but real. GraphQL means you request exactly the fields you need, so a well-written query for a product grid costs a fraction of what a lazy one costs — and on a metered API, that difference is the difference between a fast page and a throttled one.
Why Shopify API versioning is the part that bites designers
Shopify ships a new API version every three months, named by date, like 2026-10.
"Each stable version is supported for a minimum of 12 months." — Shopify API versioning docs
That sounds generous until you look at the live schedule. As of late November 2026, the latest stable version is 2026-10, 2027-01 is already a release candidate, and the oldest version still selectable in the docs is 2026-01 — which, on Shopify's published cadence of retiring versions mid-month a year after release, has about two months left. Shopify also guarantees at least nine months of overlap between consecutive versions, so nothing breaks without warning.
What happens at the deadline is worth knowing, because it is not a hard failure. Shopify "falls forward": a request pinned to a retired version gets served by the oldest version that still works. Your integration does not go dark — it quietly starts behaving differently, which is considerably harder to notice during a launch week. The real risk for an agency is a client site pinned to a version nobody has looked at since handoff.
This is also the one maintenance item that a design-led team genuinely owns. Ask your plugin or integration vendor which API version they target and how they handle upgrades. Tools built on the Storefront API — FramerLink included — should be moving versions on Shopify's cadence, not yours. We covered the practical side of one such upgrade in our notes on the 2026-07 Storefront API changes.
Where the Shopify API documentation is worth your time
Most Shopify API documentation is written for engineers, and you can safely skip the majority of it. Three pages repay the visit.
The versioning page tells you what is current and what is about to retire. The limits page tells you what your plan can actually sustain. And the Customer Account API reference matters the moment a client asks for logged-in accounts, because that flow is OAuth 2.0 with PKCE rather than a simple token — and it carries its own ceiling of 3,000 requests per minute per customer per store, shared across every app touching that shopper.
If you want the shortest path through the developer tooling itself, we mapped the parts of the Shopify developer portal designers need and skipped the rest.
What this means for your next Framer build
Keep three things in your head and you will scope these projects correctly.
The Storefront API is your front end's data source and it scales. The Admin API is server-side, metered, and never belongs in a browser. And every one of them is on a 12-month clock, which means "who upgrades the API version" is a question that belongs in the handoff document, not in a support ticket nine months later.
Everything past that — query cost, cart mutations, token rotation — is a developer's problem. Knowing where the line sits is the part that makes you useful in the room.
Frequently asked questions
What is API on Shopify?
A Shopify API is a structured way for outside software to read or change store data without using the admin interface. Shopify runs several, each scoped to a different job: the Storefront API for public catalog and cart data, the Admin API for back-office management, and the Customer Account API for logged-in buyers.
Is the Shopify API free?
Yes, in the sense that there is no separate API fee. API access is included with every Shopify plan, so the cost is whatever your store subscription already costs. What varies by plan is throughput: higher tiers get larger rate limits on the Admin API, not extra endpoints.
Is there a REST API for Shopify?
Yes, the REST Admin API still exists and still responds, but it is maintained as a legacy surface. New fields and features land in the GraphQL Admin API only, and the Storefront API and Customer Account API are GraphQL-only. Build anything new on GraphQL.
Sources
- About Shopify API versioning — Shopify
- Shopify API limits — Shopify
- GraphQL Customer Account API reference — Shopify
- Understanding Shopify's API rate limits — Shopify Partners