What it is
GraphQL is an API query language in which the client specifies exactly which fields it wants and receives precisely that, in a single request. It contrasts with REST, where the shape of each response is fixed by the endpoint and a screen often needs several calls to assemble what it shows.
Why it matters
On Salesforce it is how a Multi-Framework React app reads and writes records through the platform SDK. Asking for the fields a screen actually renders — rather than whole objects across multiple round trips — is what keeps a decoupled frontend responsive over a network you do not control.
Key components
- Client-specified field selection
- Single request per view
- Queries for reads, mutations for writes
- Typed schema
How it connects
In Salesforce it is reached through @salesforce/platform-sdk, which exposes query and mutate against the org’s GraphQL endpoint under the running user’s permissions.
Good to know
GraphQL does not bypass Salesforce security. Field-level security and sharing rules still apply — a field the user cannot see is not returned because it was asked for by name.
Related terms
Field-Level Security (FLS)
Salesforce's per-field read and edit permission control — the mechanism that keeps an Agentforce agent from seeing or changing fields it shouldn't.
Salesforce Multi-Framework
A framework-agnostic Salesforce runtime that lets a standard React app run natively on the platform, with Salesforce authentication, security and governance applied automatically.
Salesforce Platform SDK
The client library (@salesforce/platform-sdk) a Multi-Framework React app uses to query and mutate Salesforce records over GraphQL, with no authentication or token management.
GraphQL in practice
Articles from the Funnelists Team that put this term to work.
Salesforce Platform SDK Guide for Platform Architects Building React Apps
Platform architects facing React integration challenges on Salesforce can use the Platform SDK and Multi-Framework for native security and GraphQL access without custom OAuth layers.
Why Build-vs-Buy IT Leaders Decouple the Salesforce Frontend for Custom Customer Portals
Build-vs-Buy IT leaders are decoupling the Salesforce frontend to own the customer experience while keeping Salesforce as the secure, automated backend. Here is the decision framework they actually use.
How Do SF Platform Architects Implement Salesforce Micro Frontends Without Framework Lock-In?
SF Platform Architects implement Salesforce micro frontends with Multi-Framework and MFE Developer Preview using sandboxed iframes and the Platform SDK to avoid framework lock-in.
How Do SF Platform Architects Build Headless Salesforce Experiences with Multiple Frameworks?
SF Platform Architects build headless Salesforce experiences by exposing core data through APIs and composing frontends from React, LWC, Vue and more—without framework lock-in.