> 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/ltu/api-dokumentacija/geopard-api-uzklausu-apzvalga/38.-uzklausa-gauti-naudotojo-duomenis.md).

# 38. Užklausa: gauti naudotojo duomenis

Gaukite įgalioto vartotojo „UserData“.

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

```graphql
užklausa getUserData {
  getUserData {
    uuid
    el. paštas
    bendraPlotas
    maksimalusPlotas
    plotoVientis
    kalba
    apiRaktas
    dirvožemioDuomenųRinkinioKlasėsKiekis
    organizacijos {
      uuid
      pavadinimas
      pavardė
      vardas
      el. paštas
      telefonas
      sukūrimoData
      updatedDate
      vartotojai {
        organizacijosUuid
        userUuid
        el. paštas
        visosŪkis
        sukūrimoData
        updatedDate
        ūkininkavimas {
          uuid
          userUuid
          pavadinimas
          sukūrimoData
          updatedDate
          farmOwnership
          el. paštas
        }
      }
    }
  }
}
```

{% 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/ltu/api-dokumentacija/geopard-api-uzklausu-apzvalga/38.-uzklausa-gauti-naudotojo-duomenis.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.