Not necessarily. There are so many ways to obfuscate it and generally public facing graphql endpoints have introspection and all of those convenience features disabled.
To add, Twitter's backend has a bunch of layers on top of it. I did a bit of reverse engineering for my blog article on scraping Twitter [1] and there's a bit of magic token/header generation involved.
Good resource if you'd like to learn more about how the whole backend works is Nitter [2] which implements most graphql functions in Nim (it's very readable even if you don't know Nim).
To add, Twitter's backend has a bunch of layers on top of it. I did a bit of reverse engineering for my blog article on scraping Twitter [1] and there's a bit of magic token/header generation involved.
Good resource if you'd like to learn more about how the whole backend works is Nitter [2] which implements most graphql functions in Nim (it's very readable even if you don't know Nim).
1 - https://scrapfly.io/blog/how-to-scrape-twitter/#scraping-pro...
2 - https://github.com/zedeus/nitter