> For the complete documentation index, see [llms.txt](https://docs.arweavekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arweavekit.com/graphql/introduction-to-graphql.md). # Introduction to GraphQL ### Querying transaction data on Arweave As a user or developer interacting with the Arweave blockchain, there are several compelling reasons why you may need access to transaction data. For example if you're working on analytics, dApps, user interaction monitoring, verifying a transaction, smart contract interaction and the list goes on. Now accessing on-chain transactions data using REST APIs is a straight forward way to go but with GraphQL and its precise data retrieval, reduced overfetching and underfetching, batching capabilities, and real-time updates, GraphQL offers a more efficient and flexible way to interact with the Arweave blockchain. \ \ By embracing this powerful querying technology, developers can build performant and user-friendly applications, while keeping their codebase future-proof and adaptable to the evolving blockchain landscape. In this section, we will look at the following features: * Querying GraphQL endpoint for any Arweave supported blockchain data * Querying for transactions with GraphQL and cursor based pagination * Querying for all transactions with GraphQL iteratively --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.arweavekit.com/graphql/introduction-to-graphql.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.