Reaction GraphQL Implementation
Reaction GraphQL is accessible at
/graphql on the API server port.
To use GraphQL, just POST to
We recommend using a standalone GraphQL client to connect and make requests. Here are a few popular ones:
As long as you use POST method (not GET) and use the
/graphql path as the URL, requests from any GraphQL client should work. Many queries and mutations will check identity and authorization, and therefore require you to send a bearer token along with your request. Standalone GraphQL clients have a “Headers” option where you can specify this manually. See Identity and Authorization.
Identity and Authorization
Refer to Developer Concepts: Authentication
Understanding the Schema
The GraphQL schema is defined in the GraphQL server code but visible to all clients that connect as well. It governs everything that goes in or out.
Reading the API Documentation
All queries, mutations, and types in the Reaction GraphQL schema are documented within the schema itself. Go to
/graphql in a browser and click "Docs", or use your favorite standalone GraphQL client to explore the schema and read the API documentation.
Nodes and IDs
The GraphQL specification recommends globally unique IDs, and IDs in Reaction GraphQL follow this recommendation. These IDs are opaque, meaningless, and unsorted, so you should not use them for anything other than identifying an object.
Every type that has an ID implements the
Node interface. You will eventually be able to use the
Query.node query to get back any Node type without even knowing which type it is.
To understand our pagination approach, which is Relay-spec compliant, use these resources: