> For the complete documentation index, see [llms.txt](https://docs.spydra.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spydra.app/products-overview/private-network/graphql.md).

# GraphQL

### **What is Graph Query Language?**

GraphQL is a query language for APIs for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, makes it easier to evolve APIs over time, and enables powerful developer tools. For an overview of GraphQL, please refer to <https://graphql.org/>.<br>

## Spydra's GraphQL

Spydra’s QraphQL allows you to query Blockchain databases easily and efficiently. With its ability to support complex queries, you can access data in a streamlined manner. Not only can you execute simple queries based on any field of an object on the ledger, but also nested and paginated queries, as well as more complex ones. By leveraging the power of Spydra's Graph Query, you can simplify your blockchain data interactions and streamline your workflow.

You can only query data using GraphQL and we do not support modifying ledger data using mutations with GraphQL at this time.

For a list of supported queries please refer [here](/developers/api-reference/asset-tokenization/graphql.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spydra.app/products-overview/private-network/graphql.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.