Definition
The Shopify Storefront API is a GraphQL API that lets any frontend, such as a headless website, a mobile app or a kiosk, show products and collections, manage a cart and send buyers to Shopify checkout. It acts on behalf of a customer, using tokenless access or public and private tokens, and cannot change store data.
How the Storefront API works
The Storefront API is the customer side of Shopify's APIs. It lets any frontend, whether a website, a mobile app or a game, show products and collections, fill a cart and send the buyer to checkout. It is GraphQL only, with no REST version, and every request is a POST to https://your-store.myshopify.com/api/2026-10/graphql.json.[1]
What the API returns depends on how you authenticate. There are three levels:[1]
- Tokenless access needs no token at all. It covers products, collections, selling plans, search, pages, blogs and articles, and the cart, with a query complexity limit of 1,000.
- Public access token, sent in the
X-Shopify-Storefront-Access-Tokenheader, is meant for browsers and mobile apps, where anyone can see it. - Private access token, sent in the
Shopify-Storefront-Private-Tokenheader, must stay secret and is used from a server. For buyer traffic the server also sends the buyer's IP inShopify-Storefront-Buyer-IP.
Product tags, metaobjects and metafields, menus and customer data are available only with a token.[1] For international stores, the @inContext directive asks for a specific country, language, buyer identity and visitor consent, so the same query returns the right prices and translations for each market.[1]
Tokens: where they come from and what they can see
The simplest route is the Headless channel. You install it from the Shopify App Store, create a storefront, and Shopify generates a public and a private token for it. A store can have up to 100 active storefronts and access tokens.[2] Developers can also create a public token with the storefrontAccessTokenCreate mutation in the Admin API, or create a delegate token for a custom app.[1]
Each token carries unauthenticated access scopes, which are the Storefront API's permissions. They act on behalf of a customer, not a staff member. For example, unauthenticated_read_product_listings allows reading products and collections.[3] That is the key difference from the Admin API: a Storefront API token can show the catalogue and build a cart, but it cannot change a price or read another customer's orders.
| Access | Where it lives | Typical use |
|---|---|---|
| Tokenless | Anywhere | Simple product widgets, cart[1] |
| Public token | Browser or mobile app | Client-side storefronts and apps[1] |
| Private token | Server only | Server-rendered headless storefronts[1] |
Rate limits. Requests from real buyers have no fixed limit. Bots and crawlers are limited, more strictly when they are not signed, checkout creation is throttled per minute, and traffic that looks malicious gets a 430 Shopify Security Rejection.[1] So a flash sale is safe as long as the server passes the buyer's IP and the frontend does not hammer checkout.
Example: one catalogue, three storefronts
Take a hypothetical brand that sells through a headless website, an iOS app and a touchscreen kiosk in a partner shop. All three read the same Shopify catalogue and place orders in the same admin.
| Frontend | Token | Why |
|---|---|---|
| Website, rendered on a server | Private token plus buyer IP | The token stays on the server, and the buyer IP keeps buyer traffic out of bot limits[1] |
| iOS app | Public token | The token ships inside the app, so it must be the public kind[1] |
| Kiosk | Public token | Runs in a browser on a shared device |
Each frontend is its own storefront in the Headless channel, so the brand uses 3 of the 100 allowed.[2] If the kiosk token leaks, the brand revokes that one storefront without touching the website or the app. Product data that needs metafields, such as material or size charts, is fetched with a token, because tokenless access does not include metafields.[1]
Checkout still runs on Shopify. For a Serbian brand that means the payment methods configured in the admin, such as cards through CorvusPay, cash on delivery and bank transfer, work the same way as on a theme-based store, and the fiscalisation integration keeps reading orders from the admin. Our guide to Shopify Hydrogen shows how Shopify's own framework wraps the Storefront API.
Storefront API vs Admin API
| Storefront API | Admin API | |
|---|---|---|
| Acts on behalf of | A customer[3] | The store's staff or an app[3] |
| Typical use | Headless storefronts, mobile apps, product widgets | Integrations, ERP sync, back-office apps |
| Authentication | None, public token or private token[1] | Access token in X-Shopify-Access-Token[4] |
| Can change prices or orders | No; it reads the catalogue and manages carts | Yes, within its access scopes |
| Rate limits | No fixed limit for buyer traffic[1] | Cost points per second, by plan[5] |
FAQ
Is the Shopify Storefront API free?
The API has no separate fee. Access comes with the store, through tokenless access or tokens created in the Headless channel or with the Admin API. You still pay for the Shopify plan, hosting and development.[1][2]
Do I need a token for the Storefront API?
Not for basics. Tokenless access covers products, collections, search, content and the cart. Metafields, metaobjects, menus and customer data need a public or private token.[1]
Does the Storefront API have rate limits?
Not for real buyer traffic. Bots and crawlers are limited, checkout creation is throttled per minute, and requests that look malicious are rejected with a 430 error.[1]
Is the Storefront API REST or GraphQL?
GraphQL only. There is no REST version of the Storefront API.[1]
How many storefronts can one Shopify store have?
In the Headless channel, up to 100 active storefronts and access tokens per shop, each with its own token pair.[2]
The bottom line
The Storefront API is the GraphQL API that lets any frontend show a Shopify catalogue, manage a cart and hand the buyer to Shopify checkout. It acts on behalf of a customer, so it reads products and builds carts but never changes store data, which is the Admin API's job. Use public tokens in browsers and apps, private tokens on servers, and let the Headless channel issue them. If you are planning a headless build, our headless Shopify team designs the API layer first.
Article sources
We use primary sources only: official documentation, product pages and laws. Each link was checked on the date shown.
- Shopify Dev. Storefront API reference. Accessed 17th Nov 2026.
- Shopify Dev. Getting started with the Storefront API. Accessed 17th Nov 2026.
- Shopify Dev. Access scopes. Accessed 17th Nov 2026.
- Shopify Dev. GraphQL Admin API reference. Accessed 17th Nov 2026.
- Shopify Dev. GraphQL Admin API rate limits. Accessed 17th Nov 2026.
Need this on your store?
See the serviceThe checklist we run before touching a client's code
Get it by email, plus a few short notes over the next two weeks: what we see most often on Shopify stores and what actually fixes it.