The Shopify Admin API GraphQL differs from typical GraphQL APIs in two important ways: it uses a query cost budget system instead of request-count rate limiting, and it provides a Bulk Operations API for handling large datasets without hitting cost limits. This guide covers the full workflow — authentication, writing efficient queries. Use the Shopify Admin API GraphiQL explorer to test queries interactively before writing code., handling paginated data, building mutations, managing rate limits, and running bulk operations. Refer to the Shopify Admin API GraphQL reference for the complete schema.

Shopify Admin API GraphQL — authentication, query cost system, pagination, mutations and bulk operations by CodeAtoZ

Every Shopify Admin API GraphQL request requires an access token in the X-Shopify-Access-Token header. For installed apps, this token comes from the OAuth flow and must be stored server-side — never expose it to the browser. Use Shopify’s official @shopify/admin-api-client package for Node.js, which handles the correct endpoint URL, headers, and API versioning automatically. The API endpoint is https://{shop}.myshopify.com/admin/api/2025-01/graphql.json.

import {createAdminApiClient} from '@shopify/admin-api-client';
const client = createAdminApiClient({
  storeDomain: process.env.SHOPIFY_STORE_DOMAIN!,
  apiVersion: '2025-01',
  accessToken: process.env.SHOPIFY_ACCESS_TOKEN!,
});
const {data, errors, extensions} = await client.request(`
  query {
    products(first: 10) {
      edges { node { id title handle } }
    }
  }
`);
// Always check extensions.cost.throttleStatus
console.log(extensions?.cost);

The Shopify Admin API GraphQL uses a cost-based rate limiting system, not a request count limit. Each field and connection in your query has a cost value — the total query cost is checked against your store’s available budget. The response extensions.cost field shows the query cost, your current budget, and throttle status. If a query exceeds the budget, Shopify returns a 429 — retry after the number of seconds in the Retry-After header. The best defence is requesting only the fields you need. Over-fetching is the most common cause of expensive queries in the Shopify Admin API GraphQL. See the Shopify rate limits documentation for the full cost model.

The Shopify Admin API GraphQL uses cursor-based pagination via edges and nodes with pageInfo. Always request pageInfo { hasNextPage endCursor } and use after: $cursor to page forward. Mutations follow a consistent pattern — pass an input object, check userErrors in the response before assuming success, and use the returned resource for optimistic UI updates. Every mutation returns the modified object — there is no need for a follow-up query. Our Shopify development team builds apps on the Shopify Admin API GraphQL daily, and our Shopify app development guide covers the full architecture.

# Paginated query
query GetProducts($cursor: String) {
  products(first: 50, after: $cursor) {
    pageInfo { hasNextPage endCursor }
    edges { node { id title } }
  }
}
# Mutation with error handling
mutation UpdateProduct($id: ID!, $input: ProductInput!) {
  productUpdate(id: $id, input: $input) {
    product { id title }
    userErrors { field message code }
  }
}