> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/in/api/geopard-api-3/38.-userdata.md).

# 38. क्वेरी: "UserData" प्राप्त करें

अनुमोदित उपयोगकर्ता का "UserData" प्राप्त करें।

{% code overflow="wrap" lineNumbers="true" %}

```graphql
query getUserData {
  getUserData {
    uuid
    ईमेल
    कुलक्षेत्र
    अधिकतमक्षेत्र
    क्षेत्रइकाई
    भाषा
    apiKey
    मिट्टीडेटासेटवर्गोंकीमात्रा
    organizations {
      uuid
      name
      उपनाम
      प्रथमनाम
      ईमेल
      फोन
      निर्माण_तिथि
      updatedDate
      users {
        organizationUuid
        userUuid
        ईमेल
        सभीखेत
        निर्माण_तिथि
        updatedDate
        farms {
          uuid
          userUuid
          name
          निर्माण_तिथि
          updatedDate
          farmOwnership
          ईमेल
        }
      }
    }
  }
}
```

{% endcode %}


---

# 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.geopard.tech/geopard-tutorials/in/api/geopard-api-3/38.-userdata.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.