How to get query_hash?

[Kingson]

I would like to get query hash, any helpful info for me, thanks.

[alexhoma]

Hi! Here you have the specification: /docs/setup.md#how-to-get-your-query-hash-old-query-id

Into the docs/ directory you will see some examples and specifications of the library.

[Kingson]

@alexhoma Thanks for your replay, I read the docs, but I want to generate query hash by myself.
Instagram how to generate "42323d64886122307be10013ad2dcc44"?

[Kingson]

@alexhoma query_hash does not change forever?

[idkm23]

what is the point of query_hash? I would expect it would be a way from instagram to confirm the query is coming from an informed sender. But if the hash is consistent, (i.e. doesn't have a parameter like time of day) then what is the point?

[hexadeciman]

I would expect it would be a way from instagram to confirm the query is coming from an informed sender.

It is not, it's just a way for them to cache the query params so that they can store and return the response faster.
Read more here: https://stackoverflow.com/questions/54238696/what-is-query-hash-in-instagram

You should be able to generate it, using i.e. hash.js package

[jonbesga]

Hi @hexadeciman. I don't think the answer in the Stack Overflow thread is correct as the query_hash is always the same for every request (f2405b236d85e8296cf30347c9f08c2a) but the query params are differents everytime. If they were caching the query params with this method the query_hash should be different for each request.

[hexadeciman]

I just checked and it is different for every query

It just seems to stay the same for pagination.

[jonbesga]

Hmm, weird.

For example, I'm loading @mileycyrus and @instagram.

First request for both accounts has the following query hashes (the same):

Miley: aec5501414615eca36a9acf075655b1e
Instagram: aec5501414615eca36a9acf075655b1e

In successive requests, for pagination, again the same:

Miley: query_hash: f2405b236d85e8296cf30347c9f08c2a
Instagram: query_hash: f2405b236d85e8296cf30347c9f08c2a

Also, they send all the data instead of first the query_hash. So this defeats the concept of the automated persisted queries

Edit: All of this is anonymously. I'm not logged in.

[oleksiivykhor]

Hello, @Kingson, query hash you can find in browser dev tools (https://github.com/mineur/instagram-parser/blob/master/docs/setup.md#how-to-get-your-query-hash-old-query-id) and then in neighbor tab JS you can find it in one of many loaded JS files, by Ctrl + F. Then before each request you can get content of this JS file from the link in html and parse generated query hash by regex.

[webszy]

Need help for stories?how can i get stories now?

[benocd]

Does the query hash ever expire? or does it have a query limit?

[KaKi87]

Hello,
So there is no way to automatically get the query hash ?

[meshchaninov]

query_hash hardcoded in one of *.js files on instagram. If u want to get hash, u should parse js files.

[KaKi87]

Yes, I actually found out. Thanks !

[KaKi87]

Have a look at this.

[hoosnick]

@meshchaninov thanks, really it is in the static JS files.
Exactly the path: /static/bundles/metro/ConsumerLibCommons.js/gEnEraTeD_sTr.js

[Changlon]

@meshchaninov谢谢，真的是在静态 JS 文件中。 具体路径：/static/bundles/metro/ConsumerLibCommons.js/gEnEraTeD_sTr.js

i do not kown why my queryId as same as yourself ! but the name of the .js filepath was different, and i can not access your .js filepath url

[thethiny]

hash_query does not hash the variables or the parameters, it hashes the path.
Lets say your actual path is /graphql and your payload is

{
    "user": {
        "profile": [
            "username",
            "user_id",
            "profile_picture"
        ],
        "feed": {
            "posts": {
                "data": [
                    "image_url"
                ],
                "page_size": "{{variables.max_count}}"
            }
        }
    }
}

Then this graphql payload will be hashed and it becomes d4d88dc1500312af6f937f7b804c68c3. Now instead of doing that on /graphql you do /graphql/query/?query_hash=d4d88dc1500312af6f937f7b804c68c3. This way you hashed the payload, as in you hashed the "keys" that are required from the graphql. So when you pass variables as a param then the payload does not actually change, because the variables are constant as well, and you are changing them on the backend, and not in the payload.

[Skuxblan]

Any thoughts how to get query hash now days? Seems it changed and we can't get it in same way anymore