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.
Decouple Salesforce Frontend: Replace Experience Cloud with Your Own React Stack
Solution architects and Salesforce admins can now run full React apps natively on the platform. Learn how Multi-Framework removes Experience Cloud constraints while keeping data, security, and governance inside Salesforce.
Build Scalable Customer-Facing Apps on Salesforce Beyond Experience Cloud Limits
Page view caps, concurrent user limits, and API quotas are what a portal hits first. Headless architectures, React via Multi-Framework, and Agentforce deliver custom branded experiences while keeping Salesforce governance intact.
Why Are Companies Moving From Experience Cloud to Own-Code Portals?
Experience Cloud buys you speed and charges for it in licensing and rigidity. Here's when own-code portals deliver better ROI.
Salesforce GraphQL API: Enabling Efficient Headless Architectures
Discover how Salesforce GraphQL API simplifies data access in headless setups, reduces over-fetching, and supports modern frontends with built-in security and mutations.