faststore-data-fetching

FastStore custom data fetching works by defining new fields on StoreProduct through typeDefs and implementing server-side resolvers in src/graphql/vtex, then exposing them via fragments in src/fragments for server and client rendering.

The required directory structure for FastStore API extensions organizes typeDefs and resolvers in src/graphql/vtex or src/graphql/thirdParty, while client-facing query fragments reside in src/fragments to ensure build system discoverability.

FastStore secures external REST API calls by using server-side resolvers that enforce GraphQL-first data access, keeping all credential usage strictly server-only to prevent sensitive data from leaking to client-rendered scenarios.

Yes, FastStore allows extending StoreProduct with third-party data by creating API extensions with typeDefs and resolvers in src/graphql/thirdParty, then composing fragments to expose the extended data across server and client-rendered scenarios.

FastStore data fetching works for both server-rendered and client-rendered scenarios by using a fragment-driven query approach that surfaces extended data consistently across environments via the standardized src/fragments directory structure.