Token based authentication

To comply with the stateless API mode, we don't make use of cookies.

But, for graphiql, we do. /giphy flip table To make a request through the UI at /graphiql, you have to setup a cookie named _graphql_token with as value the user's token which you want to impersonate.

You can do it like this in the chrome debug console:

document.cookie="_graphql_token=your_token_here"

Mutations

mutation createPost {
  createPost(input: {title: "This is a title", content: "Some content", category_ids: [1,2], comments: [{content: "this is the first comment"}, {content: "this is the second comment"}] }) {
    post {
      title
      content
      comments {
        content
        user {
          email
        }
      }
      categories {
        name
      }
      user {
        email
      }
    }
  }
}

That answers exactly what we expect from the request, which is why graphql is perfect for frontend - backend communication. I get what I expect, nothing less, nothing more.

{
  "data": {
    "createPost": {
      "post": {
        "title": "This is a title",
        "content": "Some content",
        "comments": [
          {
            "content": "this is the second comment",
            "user": {
              "email": "[email protected]"
            }
          },
          {
            "content": "this is the first comment",
            "user": {
              "email": "[email protected]"
            }
          }
        ],
        "categories": [
          {
            "name": "Gorgeous Rubber Car"
          },
          {
            "name": "Lightweight Aluminum Table"
          }
        ],
        "user": {
          "email": "[email protected]"
        }
      }
    }
  }
}

Queries

List the 5 last posts

The (limit: 5) is actually optional and it will fallback to 30, which is what we set in the query definition.

{
  posts(limit: 5) {
    content
    title
    comments {
      content
    }
    user {
      email
    }
  }
}

Get the post with its ID

{
  post(id: 3) {
    title
    content
    comments {
      content
    }
    user {
      email
    }
  }
}