Unlike REST APIs where there is a clearly defined structure of information returned from each endpoint, GraphQL always exposes one endpoint, allowing you to determine the structure of the data that is returned.
The result of each query will be formatted in the same way as the query itself.
In the following section we’re going to have a quick look into to GraphQL components.
For a deep-dive into what you can do with GraphQL, check out the GraphQL Foundation's Introduction.
A GraphQL query performs the READ operation and does not change data.
To perform all other operations to modify data you will need mutations. You can think of mutations as CUD (Create, Update, Delete) in REST.
Object types are a collection of fields, which are used to describe the set of possible data you can query from the API.
Fields are used to ask for specific properties in objects.
Each object has fields that can be queried by name in order to query for specific properties.
You can pass arguments to a query to determine the return value (eg. filtering search results) and narrow down the results to the specific ones you’re after.
One of the most powerful parts of GraphQL is its visual interface. GraphQL playground is an in-browser tool for writing, validating, and testing GraphQL queries.
Before diving in and starting querying the API, it’s highly recommended to run your queries through the visual interface to make sure they are correct and the data being returned is the data you expect.
Variables can be used to pass dynamic values to our arguments. Variables are written outside of the query string itself, in the variables section, and passed to the arguments.
When we start working with variables, we need to do three things:
Replace the static value in the query with
$variableName as one of the variables accepted by the query
variableName: value in the separate, transport-specific (usually JSON) variables dictionary