Fork me on GitHub

@sashton thanks, I saw that. yes it does change, and is different for each authenticated user, and absent for read-only access, as it's a JWT token. I was looking for a way in development to set the Authorization header to something like Bearer bcrypt+sha512$10c72bda67f7 .... As @timgilbert suggested, a cookie could work, even though we're getting the token from an auth graphql query, not from an HTTP login. ... I just looked into it, and using an interceptor to set a cookie based on a successful auth graphql query is exactly the way I'm going to do it! Thanks, Tim for the suggestion!