GraphQL query returns { "errors": "Not Found" }

[safwanadnan]

I am writing this query: 

query {
  products(first: 10, reverse: true) {
    edges {
      node {
        id
        title
        handle
        resourcePublicationOnCurrentPublication {
          publication {
            name
            id
          }
          publishDate
          isPublished
        }
      }
    }
  }
}

This works fine for my test store but the exact same query for my actual store throws the following error:

{
    "errors": "Not Found"
}

I tried multiple different queries, all returned the same error, I checked all access scopes and access key everything is in the right place, still I get such a vague error.

Here's the actual store returning the error:

Here's the exact same query with my test store, everything else is exactly the same yet it works here:

Please help me GraphQL simply doesn't work for me.

[Liam]

On your actual store, can you install the GraphiQL app, and test the query with that? It's possible that there's an issue on Postman's side? 

[safwanadnan]

Yes works fine on the GraphiQL app but this query doesn't work on postman or using python to send requests. Both the other methods however work perfectly fine on the test store however

[Kyle_liu]

Hi @safwanadnan 

What information does this yellow symbol indicate

[safwanadnan]

I have no clue what this is, maybe this is whats causing the error, can you help me fix it?

[Kyle_liu]

Like me, take a screenshot and send it out

[safwanadnan]

[Liam]

Hi again Safwanadnan - it does sound like authorisation may not be set up correctly to make calls to the actual store.

[safwanadnan]

Can you suggest any solution, since the access token is correct to say the lease, otherwise it returns a different error and I have allowed all scopes as well, the headers are also the ones which are given in the documentation, what else am I missing?

[Kyle_liu]

Hi @safwanadnan 

In this picture, there are 10 headers. Can you share what they are? Mosaic sensitive data

[safwanadnan]

Here is my header field, I erased the access token now but it was present in the original request.