Shopify GraphQL Admin API: Practical Patterns for Developers

The Shopify Admin API moved to GraphQL in 2019. In 2026, it's the only way to access most platform features — the REST API is in maintenance mode for most endpoints. Here's what you actually need to know to use it effectively.

01Cost-based rate limiting

Shopify doesn't rate-limit by requests per second — it uses a points-based system. Each query costs points based on the fields and connections you request. You get 50 points per second, with a bucket capacity of 1,000.

# Each extensions.cost field tells you the actual cost
{
  products(first: 10) {
    edges {
      node {
        id
        title
        variants(first: 10) { # each nested connection adds cost
          edges { node { id price } }
        }
      }
    }
  }
}
# Use the throttleStatus to monitor your bucket
extensions {
  cost {
    requestedQueryCost
    actualQueryCost
    throttleStatus {
      maximumAvailable
      currentlyAvailable
      restoreRate
    }
  }
}

02Cursor-based pagination

Shopify uses cursor-based pagination — not offset pagination. There's no page=2. You get a cursor from the last item in each response and pass it as the after argument in the next query.

03Bulk operations for large datasets

If you need to fetch thousands of records (products, orders, customers), use the Bulk Operations API. It processes the query asynchronously and delivers the results as a JSONL file via a URL.

mutation {
  bulkOperationRunQuery(
    query: """
    {
      products {
        edges {
          node {
            id title
            variants {
              edges { node { id sku price } }
            }
          }
        }
      }
    }
    """
  ) {
    bulkOperation { id status }
    userErrors { field message }
  }
}

04Mutation error handling

Shopify mutations never return HTTP error codes for business logic errors — they always return 200 with a userErrors array. Always check userErrors before treating a mutation as successful.