Reaction GraphQL Implementation
Reaction GraphQL is accessible at
/graphql-alpha when running the Meteor app. You can also access it without running the Meteor app by running a Node Express server.
To run the full Meteor app from a local checkout:
docker-compose up -d reaction
To run the Node Express server only from a local checkout:
docker-compose up -d devserver
If your Reaction shop is already hosted somewhere, just POST to /graphql-alpha at that URL to use GraphQL.
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-alpha 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
We are working on a new identity and authorization system that does not rely on Meteor’s accounts system, but until that is finished, you can authenticate a GraphQL request by including a header named
meteor-login-token with a valid Meteor login token in it.
Here is how to get this login token:
- Log in to the Reaction Meteor app as the user from which you want your GraphQL requests to come.
- Open the browser console and enter
- Copy this token and set it as the value of the
meteor-login-tokenHTTP header in your GraphQL client.
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
/graphiql 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.