Hmm, I’m not seeing a forward "/graphql", Absinthe.Plug.... line in your router file at:
https://github.com/jxxcarlson/ns_umbrella/blob/graphQL/apps/lookup_phoenix/web/router.ex
Without that there the route is not exposed at /graphql, just like any other controller. 
I’m seeing this at lines 26-31 – were you in the graphQL branch?
pipeline :api do
plug :accepts, ["json"]
end
forward "/graphiql", Absinthe.Plug.GraphiQL,
schema: NoteApi.Schema
I’m seeing that too, but that is the forward for Absinthe.Plug.GraphiQL, which is the introspection helper path, but I’m not seeing a forward for forward "/graphql", Absinthe.Plug, schema: NoteApi.Schema, which is the actual path that you are having graphql communicate over?
Some progress – I now understand your point about the “other” forward. I inserted it, and if I press PLAY in GraphiQL with an empty query and http://localhost:4001/graphql in GraphiQL, I get a good error message:
{
"errors": [
{
"message": "No operations provided."
}
]
}
and I see activity in the server log. However, if I use the query
{
notes {
id
}
}
by analogy with https://www.dailydrip.com/topics/elixirsips/drips/graphql-with-absinthe, then I get the error message
“”"
Variables are invalid JSON: Unexpected token n in JSON at position 4.
“”"
Uhh, you see that in the output? If you check the browser console what was the actual body that was received? I don’t really use GraphiQL much so I’m wondering if there is a bug with that…
Now where are the absinthe devs, I know there are here somewhere…
Oops, operator error once again – I had pasted the query into the lower “Query Variables” pane. When I put it where it should be – above – all is good.
Trust me to make all possible mistakes
Thanks so much for your help!
Ahh whoo, I thought I was going crazy there for a second, I could not figure out what was wrong. ^.^;
No problem! I quite like GraphQL, and Absinthe makes it awesome in Elixir. I’ve even called in to it from the back-end of the app at times too (yay report generation!). ^.^
It is indeed awesome … there is an Elm version as well, so I will use it for both Phoenix and Elm. Yay!
Looks like my work here is done 
@jxxcarlson I highly recommend hopping on the slack channel #absinthe-graphql, there’s always quite a few people around who can help as well.