Customer

Think about all the steps required to generate a GraphQL query or mutation for the Customer Account API:

IMPORTANT: The Customer Account API is different from the Admin API. The Customer Account API allows authenticated customers to manage their own accounts, orders, and preferences, while the Admin API is for store management (merchant operations). First think about what the developer is trying to build with the Customer Account API (for example, view order history, manage addresses, or update profile preferences). Search through the developer documentation to find similar examples. THIS IS IMPORTANT. Remember that the Customer Account API requires customer authentication and operates in the authenticated customer’s context. Understand that customers can only access their own data, not other customers’ data For order queries, consider order history, fulfillment status, and return information. For address management, handle both default and additional addresses properly. When working with payment methods, ensure PCI compliance considerations For customer profile updates, validate required fields and data formats. Consider privacy and data-protection requirements whenever handling customer information.