> For the complete documentation index, see [llms.txt](https://taas-docs.stokr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taas-docs.stokr.io/api-overview/data-structure-overview.md).

# Data structure overview

Our API is built around resources in REST style, so understanding our data structure also gives you an overview of how the API is organized. We use two main categories of resources:

* **Technical resources:** Handle platform management and integrations, such as users, roles permissions, and webhook subscriptions.
* **Business resources:** Represent the core elements of your tokenization process, such as assets, investors, and wallets.

## Brief overview of the resources

The diagram below shows how these resources connect in your tokenization workflows:

<figure><picture><source srcset="/files/dvZ9aekBntOhdaodFUX7" media="(prefers-color-scheme: dark)"><img src="/files/HM7uEUsdhPYX2MM9KkWm" alt=""></picture><figcaption></figcaption></figure>

Each resource is explained in detail on the related pages, but below you can find a very brief overview:

{% tabs %}
{% tab title="Technical resources" %}

* [User](/api-overview/users-and-roles.md): User account for accessing our API, representing either your employees or technical systems (monitoring, data sync, etc.)
* [Permission](/api-overview/users-and-roles.md): Specific action that a user can perform on the platform
* [Role](/api-overview/users-and-roles.md): Collection of permissions grouped together for easier user management
* Webhook subscription: Setup for receiving real-time notifications about specific events
  {% endtab %}

{% tab title="Business resources" %}

* [Investor](/asset-distribution/asset-distribution-process/onboarding-investors.md): Person or legal entity who can hold your tokenized assets
* [Investor wallet](/asset-distribution/asset-distribution-process/assigning-tokens.md): Blockchain wallet where an investor receives and holds tokens
* [Issuer](/asset-origination/asset-origination-process/setting-up-issuer.md): Your organization or legal entity that's tokenizing assets
* [Asset](/asset-origination/asset-origination-process/onboarding-an-asset.md): The financial instrument you're tokenizing, along with its configuration and parameters
* [Treasury wallet](/asset-origination/asset-origination-process/onboarding-an-asset.md): Your organization's blockchain wallet for a specific asset, used for issuing or redeeming tokens
* [Whitelist](/asset-origination/asset-origination-process/setting-up-whitelist.md): Approved group of investors who are authorized to purchase and hold tokens for specific assets
* [Investment](/asset-distribution/asset-subscription-process/placing-an-investment.md): Record of tokens allocated to an investor during primary distribution
* Transaction: Record of token movements on the blockchain
  {% endtab %}
  {% endtabs %}


---

# 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://taas-docs.stokr.io/api-overview/data-structure-overview.md?ask=<question>&goal=<endgoal>
```

`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.